Home | Trees | Indices | Help |
---|
|
object --+ | transport.Transport --+ | Connection
Connection to server.
Represents a connection to a server and handles all socket operations and request/response dispatch.
|
|||
SessionSetupContext |
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Inherited from Inherited from |
|
|||
Client |
client The Client object associated with this connection. |
||
port The server port |
|||
server The server name or address |
|
|||
Inherited from |
|
Constructor. This should generally not be used directly. Instead, use Client.connect().
|
Register a callback function for the context block, then unregister it
|
Registers a callback function, cb for the given event. When the event fires, cb will be called with the relevant top-level Netbios frame as the single paramter. |
Fire callbacks for the given event, passing obj as the parameter Connection-specific callbacks will be fired first, followed by client callbacks |
multicredit requests must reserve 1 message id per credit charged. the message id of the request should be the first id of the range. |
callback fired when connection is established
|
callback fired when the socket has data available
|
callback fired when the socket is available for writing note: unlike asyncore, write notifications are not provided by default. this is a performance optimization because the socket is usually available for writing, and the application usually knows when it wants to write. There is no point in filling the event queues with write ready messages that will be ignored if the client has no data to send. Instead, applications are expected to implement handle_write, but to call it directly when data is to be sent. IF the socket would block, EALREADY will be handled by the Transport. The Transport requests a single write notification from the pollwer; when received, handle_write will be called once signalling that the socket may now be ready to retry If the application would prefer to be notified when the socket is ready to write, transport.poller.defer_write(transport) may be called to schedule a single handle_write callback.
|
callback fired when the socket is closed
|
callback fired if a non-recoverable exception is raised
|
Close connection. This unceremoniously terminates the connection and fails all outstanding requests with EOFError.
|
Submit request. Submits a netbios.Netbios frame for sending. Returns a list of Future objects, one for each corresponding smb2.Smb2 frame in the request. |
Submit request and wait for responses. Submits a netbios.Netbios frame for sending. Waits for and returns a list of smb2.Smb2 response objects, one for each corresponding smb2.Smb2 frame in the request. |
Perform dialect negotiation. This must be performed before setting up a session with Connection.session_setup(). |
Establish a session. Establishes a session, performing GSS rounds as necessary. Returns a Channel object which can be used for further requests on the given connection and session. |
Home | Trees | Indices | Help |
---|
Generated by Epydoc 3.0.1 on Thu Jun 29 08:51:17 2017 | http://epydoc.sourceforge.net |