ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/cvsroot/AnyEvent-Porttracker/Porttracker.pm
(Generate patch)

Comparing cvsroot/AnyEvent-Porttracker/Porttracker.pm (file contents):
Revision 1.4 by root, Mon Nov 15 20:41:17 2010 UTC vs.
Revision 1.5 by root, Mon Nov 15 20:43:11 2010 UTC

24run a supported event loop. 24run a supported event loop.
25 25
26To quickly understand how this module works you should read how to 26To quickly understand how this module works you should read how to
27construct a new connection object and then read about the event/callback 27construct a new connection object and then read about the event/callback
28system. 28system.
29
30The actual low-level protocol and, more importantly, the existing
31requests and responses, are documented in the official Porttracker
32API documentation (a copy of which is included in this module as
33L<AnyEvent::Porttracker::protocol>.
29 34
30=head1 THE AnyEvent::Porttracker CLASS 35=head1 THE AnyEvent::Porttracker CLASS
31 36
32The AnyEvent::Porttracker class represents a single connection. 37The AnyEvent::Porttracker class represents a single connection.
33 38
189 194
190Sends a generic request of type C<$type> to the server. When the server 195Sends a generic request of type C<$type> to the server. When the server
191responds, the API object and the response arguments are passed to the 196responds, the API object and the response arguments are passed to the
192callback, which is the last argument to this method. 197callback, which is the last argument to this method.
193 198
199The available requests are documented in the Porttracker API
200documentation (a copy of which is included in this module as
201L<AnyEvent::Porttracker::protocol>.
202
194It is permissible to call this (or any other request function) at any 203It is permissible to call this (or any other request function) at any
195time, even before the connection has been established - the API object 204time, even before the connection has been established - the API object
196always waits until after login before it actually sends the requests, and 205always waits until after login before it actually sends the requests, and
197queues them until then. 206queues them until then.
198 207

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines