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