Some more methods under dispatcher class














































Some more methods under dispatcher class



Methods under Dispatcher class:

1)readable()
Called each time around the asynchronous loop to determine whether a channel's socket should be added to the list on which read events can occur. The default method simply returns True, indicating that by default, all channels will be interested in read events.

2)writable()
Called each time around the asynchronous loop to determine whether a channel%u2019s socket should be added to the list on which write events can occur. The default method simply returns True, indicating that by default, all channels will be interested in write events.

In addition, each channel delegates or extends many of the socket methods. Most of these are nearly identical to their socket partners.

3)create_socket(family=socket.AF_INET, type=socket.SOCK_STREAM)
This is identical to the creation of a normal socket, and will use the same options for creation. Refer to the socket documentation for information on creating sockets.

4)connect(address)
As with the normal socket object, address is a tuple with the first element the host to connect to, and the second the port number.

5)send(data)
Send data to the remote end-point of the socket.

6)recv(buffer_size)
Read at most buffer_size bytes from the socket%u2019s remote end-point. An empty bytes object implies that the channel has been closed from the other end.

7)listen(backlog)
Listen for connections made to the socket. The backlog argument specifies the maximum number of queued connections and should be at least 1; the maximum value is system-dependent (usually 5).

8)bind(address)
Bind the socket to address. The socket must not already be bound. (The format of address depends on the address family %u2014 refer to the socket documentation for more information.) To mark the socket as re-usable (setting the SO_REUSEADDR option), call the dispatcher object%u2019s set_reuse_addr() method.

9)accept()
Accept a connection. The socket must be bound to an address and listening for connections. The return value can be either None or a pair (conn, address) where conn is a new socket object usable to send and receive data on the connection, and address is the address bound to the socket on the other end of the connection. When None is returned it means the connection didn%u2019t take place, in which case the server should just ignore this event and keep listening for further incoming connections.

10)close()
Close the socket. All future operations on the socket object will fail. The remote end-point will receive no more data (after queued data is flushed). Sockets are automatically closed when they are garbage-collected.

Comments