POEx::IRC::Backend::Connect - A connected IRC socket
Typically created by POEx::IRC::Backend to represent an established connection.
This class consumes the following roles:
Connected socket wheels normally have a POE alarm ID attached for an idle timer.
Boolean true if the Zlib filter has been added.
Change the boolean value of the "compressed" attrib.
Idle time used for connection check alarms.
Boolean false if the Connect is not in a disconnecting state; if it is true, it is the disconnect message:
See also: "disconnect" in POEx::IRC::Backend
Boolean true if the connection wheel has been marked as a client.
Boolean true if the connection wheel has been marked as a peer.
Primarily for internal use; boolean true if the Wheel needs a Zlib filter on next buffer flush.
ping_pending attribute can be used to manage standard IRC PING/PONG heartbeating; a server can call
$conn->ping_pending(1) upon dispatching a PING to a client (because of an
ircsock_connection_idle event, for example) and
$conn->ping_pending(0) when a response is received.
$conn->ping_pending is true on the next
ircsock_connection_idle, the client can be considered to have timed out and your server-side
Backend can issue a disconnect; this emulates standard IRCD behavior.
The remote peer address.
The remote peer port.
Timestamp of last socket activity; updated by POEx::IRC::Backend when traffic is seen from this Connect.
Our socket address.
Our socket port.
Returns the actual underlying socket handle, or undef if one is not open.
If this is a SSLified socket, the real handle is retrieved via "SSLify_GetSocket" in POE::Component::SSLify.
Returns the cipher in use by calling "SSLify_GetCipher" in POE::Component::SSLify, or the empty string if this is not an SSLified connection.
Jon Portnoy <email@example.com>