Examples of ClientSession

com.facebook.presto.client.ClientSession
com.facebook.presto.jdbc.internal.client.ClientSession
com.google.code.sshd.ClientSession
com.kurento.kmf.jsonrpcconnector.internal.client.ClientSession
com.sun.sgs.app.ClientSession
Interface representing a single, connected login session between a client and the server. Classes that implement {@code ClientSession} must also implement {@link Serializable}.
When a client logs in, the application's {@link AppListener#loggedIn(ClientSession) AppListener.loggedIn} method isinvoked with a new {@code ClientSession} instance which represents thecurrent connection between that client and the server. By returning a unique {@link ClientSessionListener} from the {@code loggedIn} methodfor each given client session, the application will receive notification when a client session sends a message, is disconnected, or logs out. To explicitly disconnect a {@code ClientSession}, remove the associated {@code ClientSession} object from the data manager using the {@link DataManager#removeObject DataManager.removeObject} method.
A {@code ClientSession} is used to identify a client that islogged in, to send messages to that client, and to forcibly disconnect that client from the server.
A session is considered disconnected if one of the following occurs:
- the client logs out
- the client becomes disconnected due to a network failure, and a connection to the client cannot be re-established in a timely manner
- the {@code ClientSession} object is removed from the data manager
If a client associated with a {@code ClientSession} becomesdisconnected due to one of these conditions, the {@link ClientSessionListener#disconnected(boolean) disconnected} method isinvoked on that session's registered {@code ClientSessionListener} with a {@code boolean} thatif {@code true} indicates the client logged out gracefully.
Once a client becomes disconnected, its {@code ClientSession}becomes invalid and can no longer be used to communicate with that client and should be removed from the data manager. When that client logs back in again, a new session is established with the server.
oracle.toplink.essentials.threetier.ClientSession
Purpose: Acts as a client to the server session.
Description: This session is brokered by the server session for use in three-tiered applications. It is used to store the context of the connection, i.e. the login to be used for this cleint. This allows each client connected to the server to contain its own user login.
Responsibilities:
- Allow units of work to be acquired and pass them the client login's exclusive connection.
- Forward all requests and queries to its parent server session.
This class is an implementation of {@link oracle.toplink.essentials.sessions.Session}. Please refer to that class for a full API. The public interface should be used. @see Server @see oracle.toplink.essentials.sessions.UnitOfWork
org.apache.chemistry.opencmis.workbench.model.ClientSession
org.apache.qpid.nclient.impl.ClientSession
Implements a Qpid Sesion.
org.apache.sshd.ClientSession
An authenticated session to a given SSH server A client session is established using the {@link SshClient}. Once the session has been created, the user has to authenticate using either {@link #authPassword(String,String)} or{@link #authPublicKey(String,java.security.KeyPair)}. From this session, channels can be created using the {@link #createChannel(String)} method. Multiple channels canbe created on a given session concurrently. When using the client in an interactive mode, the {@link #waitFor(int,long)} method can be used to listen to specificevents such as the session being established, authenticated or closed. When a given session is no longer used, it must be closed using the {@link #close(boolean)} method. @author Apache MINA SSHD Project
org.eclipse.persistence.sessions.server.ClientSession
Purpose: Acts as a client to the server session.
Description: This session is brokered by the server session for use in three-tiered applications. It is used to store the context of the connection, i.e. the login to be used for this client. This allows each client connected to the server to contain its own user login.
Responsibilities:
- Allow units of work to be acquired and pass them the client login's exclusive connection.
- Forward all requests and queries to its parent server session.
This class is an implementation of {@link org.eclipse.persistence.sessions.Session}. Please refer to that class for a full API. The public interface should be used. @see Server @see org.eclipse.persistence.sessions.Session @see org.eclipse.persistence.sessions.UnitOfWork
org.hornetq.api.core.client.ClientSession
A ClientSession is a single-thread object required for producing and consuming messages. @author Tim Fox @author Clebert Suconic @author Andy Taylor @author Jeff Mesnil
org.jivesoftware.openfire.session.ClientSession
Represents a session between the server and a client. @author Gaston Dombiak
org.openbp.core.remote.ClientSession
This class represents a connection the client is maintaining with the OpenBP server. @author Falk Hartmann

Examples of org.openbp.core.remote.ClientSession

      .lookupOptionalService(ModelNotificationService.class);
    if (mns != null)
    {
      try
      {
        ClientSession session = ServerConnection.getInstance().getSession();
        ModelQualifier qualifier = event.getQualifier();
        String eventType = event.getEventType();


        // Notify the server from the model changes
        if (eventType == ModelConnectorEvent.MODEL_ADDED || eventType == ModelConnectorEvent.ITEM_ADDED)

View Full Code Here

0 1 2 3 4 5 6

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.