Uses of Package
org.jivesoftware.openfire.session
Packages that use org.jivesoftware.openfire.session
Package
Description
Service that records XMPP traffics.
Implementation of XEP-0352 "Client State Indication"
It is common for IM clients to be logged in and 'online' even while the user is not interacting with the application.
Service discovery implementation (XEP-0030).
Event system.
Provides classes for XEP-0124: Bidirectional-streams Over Synchronous HTTP (BOSH).
Provides classes for intercepting packets.
Connection Manager implementation.
Implementation of Personal Eventing via Pubsub (XEP-0163).
Provides classes for SASL.
Classes used for server-to-server communication.
Provides the interfaces and classes necessary to create custom
user account data providers for Openfire.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfireClassDescriptionRepresents a session between the server and a client.Client session information to be used when running in a cluster.Represents a session between the server and an external component.Represents a session between the server and a connection manager.Holds a (possibly authenticated) domain pair.Server-to-server communication is done using two TCP connections between the servers.Represents a session between the server and a client.Represents a session between the server and a component.Represents a session between the server and a connection manager.Server-to-server communication is done using two TCP connections between the servers.Server-to-server communication is done using two TCP connections between the servers.The session represents a connection between the server and a client (c2s) or another server (s2s) as well as a connection with a component.Server-to-server communication is done using two TCP connections between the servers.Locator of sessions that are being hosted by other cluster nodes.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.auditClassDescriptionThe session represents a link (often a socket connection) between the server and a remote XMPP entity.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.audit.spiClassDescriptionThe session represents a link (often a socket connection) between the server and a remote XMPP entity.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.csi
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.discoClassDescriptionThe session represents a connection between the server and a client (c2s) or another server (s2s) as well as a connection with a component.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.eventClassDescriptionThe session represents a link (often a socket connection) between the server and a remote XMPP entity.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.httpClassDescriptionRepresents a session between the server and a client.Represents a session between the server and a client.The session represents a connection between the server and a client (c2s) or another server (s2s) as well as a connection with a component.The session represents a link (often a socket connection) between the server and a remote XMPP entity.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.interceptorClassDescriptionThe session represents a link (often a socket connection) between the server and a remote XMPP entity.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.multiplexClassDescriptionRepresents a session between the server and a connection manager.Represents a session between the server and a client.The session represents a link (often a socket connection) between the server and a remote XMPP entity.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.netClassDescriptionRepresents a session between the server and a client.Holds a (possibly authenticated) domain pair.Server-to-server communication is done using two TCP connections between the servers.The session represents a connection between the server and a client (c2s) or another server (s2s) as well as a connection with a component.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.nioClassDescriptionHolds a (possibly authenticated) domain pair.The session represents a connection between the server and a client (c2s) or another server (s2s) as well as a connection with a component.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.pep
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.saslClassDescriptionRepresents a session between the server and a client.Server-to-server communication is done using two TCP connections between the servers.The session represents a connection between the server and a client (c2s) or another server (s2s) as well as a connection with a component.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.serverClassDescriptionHolds a (possibly authenticated) domain pair.Server-to-server communication is done using two TCP connections between the servers.Server-to-server communication is done using two TCP connections between the servers.Server-to-server communication is done using two TCP connections between the servers.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.sessionClassDescriptionRepresents a session between the server and a client.Represents a session between the server and an external component.The ExternalComponent acts as a proxy of the remote connected component.Represents a session between the server and a connection manager.Holds a (possibly authenticated) domain pair.Server-to-server communication is done using two TCP connections between the servers.Represents a session between the server and a client.Represents a session between the server and a component.Represents a session between the server and a connection manager.Server-to-server communication is done using two TCP connections between the servers.The session represents a connection between the server and a client (c2s) or another server (s2s) as well as a connection with a component.Server-to-server communication is done using two TCP connections between the servers.Base class for sessions being hosted in other cluster nodes.Locator of sessions that are being hosted by other cluster nodes.Operations to be executed in a remote session hosted in a remote cluster node.The session represents a link (often a socket connection) between the server and a remote XMPP entity.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.spiClassDescriptionRepresents a session between the server and a client.Holds a (possibly authenticated) domain pair.Represents a session between the server and a client.Server-to-server communication is done using two TCP connections between the servers.Server-to-server communication is done using two TCP connections between the servers.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.streammanagementClassDescriptionThe session represents a connection between the server and a client (c2s) or another server (s2s) as well as a connection with a component.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.user
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.openfire.websocketClassDescriptionRepresents a session between the server and a client.The session represents a connection between the server and a client (c2s) or another server (s2s) as well as a connection with a component.
-
Classes in org.jivesoftware.openfire.session used by org.jivesoftware.util.cacheClassDescriptionRepresents a session between the server and a client.Client session information to be used when running in a cluster.Holds a (possibly authenticated) domain pair.Incoming server session information to be used when running in a cluster.Represents a session between the server and a client.Server-to-server communication is done using two TCP connections between the servers.Server-to-server communication is done using two TCP connections between the servers.