- All Superinterfaces:
- All Known Implementing Classes:
public interface OutgoingServerSession extends ServerSessionServer-to-server communication is done using two TCP connections between the servers. One connection is used for sending packets while the other connection is used for receiving packets. The
OutgoingServerSessionrepresents the connection to a remote server that will only be used for sending packets.
Once the connection has been established with the remote server and at least a domain has been authenticated then a new route will be added to the routing table for this connection. For optimization reasons the same outgoing connection will be used even if the remote server has several hostnames. However, different routes will be created in the routing table for each hostname of the remote server.
- Gaston Dombiak
All Methods Instance Methods Abstract Methods Modifier and Type Method Description
addOutgoingDomainPair(String local, String remote)Marks a domain pair as being authenticated.
authenticateSubdomain(String domain, String hostname)Authenticates a subdomain of this server with the specified remote server over an exsiting outgoing connection.
checkOutgoingDomainPair(String local, String remote)Checks to see if a pair of domains has previously been authenticated.
getOutgoingDomainPairs()Obtains all authenticated domain pairs.
Methods inherited from interface org.jivesoftware.openfire.session.ServerSession
Methods inherited from interface org.jivesoftware.openfire.session.Session
close, deliverRawText, getAddress, getCipherSuiteName, getCreationDate, getHostAddress, getHostName, getLanguage, getLastActiveDate, getNumClientPackets, getNumServerPackets, getPeerCertificates, getServerName, getSoftwareVersion, getStatus, getStreamID, isClosed, isSecure, process, validate
authenticateSubdomainAuthenticates a subdomain of this server with the specified remote server over an exsiting outgoing connection. If the existing session was using server dialback then a new db:result is going to be sent to the remote server. But if the existing session was TLS+SASL based then just assume that the subdomain was authenticated by the remote server.
domain- the locally domain to authenticate with the remote server.
hostname- the domain of the remote server.
- True if the domain was authenticated by the remote server.
checkOutgoingDomainPairChecks to see if a pair of domains has previously been authenticated. Since domains are authenticated as pairs, authenticating A->B does not imply anything about A-->C or D->B.
local- the local domain (previously: authenticated domain)
remote- the remote domain (previous: hostname)
- True if the pair of domains has been authenticated.
addOutgoingDomainPairMarks a domain pair as being authenticated.
local- the locally hosted domain.
remote- the remote domain.