Connection is used to establish an encrypted TCP/IP connection to a SSH-2 server. Typically, one
Connection extends Globals Connection from which it inherits all basic communication entry points. In addition to that it also servers as a DocumentMap factory, and provides schema management methods.
To connect to a broker, fill in a {@link ConnectionFactory} and use a {@link ConnectionFactory} as follows:
ConnectionFactory factory = new ConnectionFactory(); factory.setHost(hostName); factory.setPort(portNumber); factory.setVirtualHost(virtualHost); factory.setUsername(username); factory.setPassword(password); Connection conn = factory.newConnection(); // Then open a channel: Channel channel = conn.createChannel();Or, more compactly:
ConnectionFactory factory = new ConnectionFactory(); factory.setUri("amqp://username:password@hostName:portNumber/virtualHost"); Connection conn = factory.newConnection(); Channel channel = conn.createChannel() Current implementations are thread-safe for code at the client API level, and in fact thread-safe internally except for code within RPC calls.
Encapsulates Salesforce.com connection functionality.
There are four separate WSDLs that we are consuming and each one has a different endpoint:
@author cwall
Connection represents a transport in the PEPt architecture.
A Connection represents a bi-directional communication channel between a debugger and a target VM. A Connection is created when {@link com.sun.jdi.connect.spi.TransportService TransportService}establishes a connection and successfully handshakes with a target VM. A TransportService implementation provides a reliable JDWP packet transportation service and consequently a Connection provides a reliable flow of JDWP packets between the debugger and the target VM. A Connection is stream oriented, that is, the JDWP packets written to a connection are read by the target VM in the order in which they were written. Similiarly packets written to a Connection by the target VM are read by the debugger in the order in which they were written.
A connection is either open or closed. It is open upon creation, and remains open until it is closed. Once closed, it remains closed, and any attempt to invoke an I/O operation upon it will cause a {@link ClosedConnectionException} to be thrown. A connection canbe tested by invoking the {@link #isOpen isOpen} method.
A Connection is safe for access by multiple concurrent threads, although at most one thread may be reading and at most one thread may be writing at any given time.
@since 1.5Connection is used to establish an encrypted TCP/IP connection to a SSH-2 server. Typically, one
Important Note : if you wish to use synchronous mode in a multi-threaded environment, it is the application's responsiblity to ensure there is only one thread executing a call to either or both of the sendRequest and readNextPacket methods. If there are concurrent calls to these methods executing, there is a strong possibility of the incorrect packet being returned in a particular thread and both the API and the application getting confused. These are the only methods that contain such a race condition.
A Connection represents a session with a specific database. Within the context of a Connection, SQL statements are executed and results are returned.
A Connection's database is able to provide information describing its tables, its supported SQL grammar, its stored procedures, the capabilities of this connection, etc. This information is obtained with the getMetaData method.
Note: By default the Connection automatically commits changes after executing each statement. If auto commit has been disabled, an explicit commit must be done or database changes will not be saved. @see DriverManager#getConnection @see Statement @see ResultSet @see DatabaseMetaData
Connection implementation typically contains a {@link Socket}. Connection is implemented by connection-based {@link Endpoint} implementations that use {@link ConnectionManager}for managing connections. A Connection is created by the implementation for newly-established connections and is obtained by a ConnectionManager from its {@link ConnectionEndpoint}'s connect methods.
@author Sun Microsystems, Inc.
@since 2.0
Connections also manage the life-cycle of UserInstances within the HttpSession.
Connection objects are obtained using {@link ConnectionManager#connect()}.
@author Mike Heath
@see DbSession
@see ConnectionManager
The connection object contains logic to find the master, locate regions out on the cluster, keeps a cache of locations and then knows how to re-calibrate after they move. The individual connections to servers, meta cache, zookeeper connection, etc are all shared by the {@link Table} and {@link Admin} instances obtained from this connection.
Connection creation is a heavy-weight operation. Connection implementations are thread-safe, so that the client can create a connection once, and share it with different threads. {@link Table} and {@link Admin} instances, on the other hand, are light-weight and are notthread-safe. Typically, a single connection per client application is instantiated and every thread will obtain its own Table instance. Caching or pooling of {@link Table} and {@link Admin}is not recommended.
This class replaces {@link HConnection}, which is now deprecated. @see ConnectionFactory
NetworkConnection encapsulates the properties associated with a connection to a TCP/IP network. The network connection describes one TCP port on one network device. This can be used for a TCP connection over which a DICOM association can be negotiated with one or more Network AEs. It specifies 8 the hostname and TCP port number. A network connection may support multiple Network AEs. The Network AE selection takes place during association negotiation based on the called and calling AE-titles.
@author Gunter Zeilinger
A {@link Connection} is associated to an {@link EndPoint} so that I/O eventshappening on the {@link EndPoint} can be processed by the {@link Connection}.
A typical implementation of {@link Connection} overrides {@link #onOpen()} to{@link EndPoint#fillInterested(Callback) set read interest} on the {@link EndPoint}, and when the {@link EndPoint} signals read readyness, this {@link Connection} canread bytes from the network and interpret them.
Connection represents an application-level handle that is used by a client to access the underlying physical connection. The actual physical connection associated with a Connection instance is represented by a ManagedConnection instance.
@author Tim Anderson
@version $Revision: 1.2 $ $Date: 2005/11/16 12:32:49 $
@see ManagedConnection
If a connected Connection gets disconnected abruptly then it will try to reconnect again. To stop the reconnection process, use {@link #disconnect()}. Once stopped you can use {@link #connect()} to manually connect to the server. @see XMPPConnection @author Matt Tucker @author Guenther Niess
To get a new Connection, use {@link org.jsoup.Jsoup#connect(String)}. Connections contain {@link Connection.Request}and {@link Connection.Response} objects. The request objects are reusable as prototype requests.
Request configuration can be made using either the shortcut methods in Connection (e.g. {@link #userAgent(String)}), or by methods in the Connection.Request object directly. All request configuration must be made before the request is executed.
The Connection interface is currently in beta and subject to change. Comments, suggestions, and bug reports are welcome.
javax.jms.Connection interface. A Connection object allows the client's active connection to the Joram server. Connections support concurrent use, it serves several purposes:
Connection object is used to manage connections from a server socket. In order to achieve this it spawns a task to listen for incoming connect requests. When a TCP connection request arrives it hands off the SocketChannel to the Server which processes the request. This handles connections from a ServerSocketChannel object so that features such as SSL can be used by a server that uses this package. The background acceptor process will terminate if the connection is closed.
@author Niall Gallagher
@see org.simpleframework.transport.Server
Session, Transmitter and Receiver classes use this class for sending and receiving data to and from SMSC.
@author Logica Mobile Networks SMPP Open Source Team
@version $Revision: 1.3 $
@see TCPIPConnection
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |