1 | package AnyEvent::Handle; |
1 | package AnyEvent::Handle; |
2 | |
2 | |
3 | no warnings; |
3 | no warnings; |
4 | use strict; |
4 | use strict qw(subs vars); |
5 | |
5 | |
6 | use AnyEvent (); |
6 | use AnyEvent (); |
7 | use AnyEvent::Util qw(WSAEWOULDBLOCK); |
7 | use AnyEvent::Util qw(WSAEWOULDBLOCK); |
8 | use Scalar::Util (); |
8 | use Scalar::Util (); |
9 | use Carp (); |
9 | use Carp (); |
… | |
… | |
14 | |
14 | |
15 | AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent |
15 | AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent |
16 | |
16 | |
17 | =cut |
17 | =cut |
18 | |
18 | |
19 | our $VERSION = 4.15; |
19 | our $VERSION = 4.233; |
20 | |
20 | |
21 | =head1 SYNOPSIS |
21 | =head1 SYNOPSIS |
22 | |
22 | |
23 | use AnyEvent; |
23 | use AnyEvent; |
24 | use AnyEvent::Handle; |
24 | use AnyEvent::Handle; |
… | |
… | |
49 | |
49 | |
50 | This module is a helper module to make it easier to do event-based I/O on |
50 | This module is a helper module to make it easier to do event-based I/O on |
51 | filehandles. For utility functions for doing non-blocking connects and accepts |
51 | filehandles. For utility functions for doing non-blocking connects and accepts |
52 | on sockets see L<AnyEvent::Util>. |
52 | on sockets see L<AnyEvent::Util>. |
53 | |
53 | |
|
|
54 | The L<AnyEvent::Intro> tutorial contains some well-documented |
|
|
55 | AnyEvent::Handle examples. |
|
|
56 | |
54 | In the following, when the documentation refers to of "bytes" then this |
57 | In the following, when the documentation refers to of "bytes" then this |
55 | means characters. As sysread and syswrite are used for all I/O, their |
58 | means characters. As sysread and syswrite are used for all I/O, their |
56 | treatment of characters applies to this module as well. |
59 | treatment of characters applies to this module as well. |
57 | |
60 | |
58 | All callbacks will be invoked with the handle object as their first |
61 | All callbacks will be invoked with the handle object as their first |
… | |
… | |
70 | |
73 | |
71 | =item fh => $filehandle [MANDATORY] |
74 | =item fh => $filehandle [MANDATORY] |
72 | |
75 | |
73 | The filehandle this L<AnyEvent::Handle> object will operate on. |
76 | The filehandle this L<AnyEvent::Handle> object will operate on. |
74 | |
77 | |
75 | NOTE: The filehandle will be set to non-blocking (using |
78 | NOTE: The filehandle will be set to non-blocking mode (using |
76 | AnyEvent::Util::fh_nonblocking). |
79 | C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in |
|
|
80 | that mode. |
77 | |
81 | |
78 | =item on_eof => $cb->($handle) |
82 | =item on_eof => $cb->($handle) |
79 | |
83 | |
80 | Set the callback to be called when an end-of-file condition is detcted, |
84 | Set the callback to be called when an end-of-file condition is detected, |
81 | i.e. in the case of a socket, when the other side has closed the |
85 | i.e. in the case of a socket, when the other side has closed the |
82 | connection cleanly. |
86 | connection cleanly. |
83 | |
87 | |
|
|
88 | For sockets, this just means that the other side has stopped sending data, |
|
|
89 | you can still try to write data, and, in fact, one can return from the eof |
|
|
90 | callback and continue writing data, as only the read part has been shut |
|
|
91 | down. |
|
|
92 | |
84 | While not mandatory, it is highly recommended to set an eof callback, |
93 | While not mandatory, it is I<highly> recommended to set an eof callback, |
85 | otherwise you might end up with a closed socket while you are still |
94 | otherwise you might end up with a closed socket while you are still |
86 | waiting for data. |
95 | waiting for data. |
|
|
96 | |
|
|
97 | If an EOF condition has been detected but no C<on_eof> callback has been |
|
|
98 | set, then a fatal error will be raised with C<$!> set to <0>. |
87 | |
99 | |
88 | =item on_error => $cb->($handle, $fatal) |
100 | =item on_error => $cb->($handle, $fatal) |
89 | |
101 | |
90 | This is the error callback, which is called when, well, some error |
102 | This is the error callback, which is called when, well, some error |
91 | occured, such as not being able to resolve the hostname, failure to |
103 | occured, such as not being able to resolve the hostname, failure to |
92 | connect or a read error. |
104 | connect or a read error. |
93 | |
105 | |
94 | Some errors are fatal (which is indicated by C<$fatal> being true). On |
106 | Some errors are fatal (which is indicated by C<$fatal> being true). On |
95 | fatal errors the handle object will be shut down and will not be |
107 | fatal errors the handle object will be shut down and will not be usable |
|
|
108 | (but you are free to look at the current C<< ->rbuf >>). Examples of fatal |
|
|
109 | errors are an EOF condition with active (but unsatisifable) read watchers |
|
|
110 | (C<EPIPE>) or I/O errors. |
|
|
111 | |
96 | usable. Non-fatal errors can be retried by simply returning, but it is |
112 | Non-fatal errors can be retried by simply returning, but it is recommended |
97 | recommended to simply ignore this parameter and instead abondon the handle |
113 | to simply ignore this parameter and instead abondon the handle object |
98 | object when this callback is invoked. |
114 | when this callback is invoked. Examples of non-fatal errors are timeouts |
|
|
115 | C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>). |
99 | |
116 | |
100 | On callback entrance, the value of C<$!> contains the operating system |
117 | On callback entrance, the value of C<$!> contains the operating system |
101 | error (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT> or C<EBADMSG>). |
118 | error (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT> or C<EBADMSG>). |
102 | |
119 | |
103 | While not mandatory, it is I<highly> recommended to set this callback, as |
120 | While not mandatory, it is I<highly> recommended to set this callback, as |
… | |
… | |
124 | This sets the callback that is called when the write buffer becomes empty |
141 | This sets the callback that is called when the write buffer becomes empty |
125 | (or when the callback is set and the buffer is empty already). |
142 | (or when the callback is set and the buffer is empty already). |
126 | |
143 | |
127 | To append to the write buffer, use the C<< ->push_write >> method. |
144 | To append to the write buffer, use the C<< ->push_write >> method. |
128 | |
145 | |
|
|
146 | This callback is useful when you don't want to put all of your write data |
|
|
147 | into the queue at once, for example, when you want to write the contents |
|
|
148 | of some file to the socket you might not want to read the whole file into |
|
|
149 | memory and push it into the queue, but instead only read more data from |
|
|
150 | the file when the write queue becomes empty. |
|
|
151 | |
129 | =item timeout => $fractional_seconds |
152 | =item timeout => $fractional_seconds |
130 | |
153 | |
131 | If non-zero, then this enables an "inactivity" timeout: whenever this many |
154 | If non-zero, then this enables an "inactivity" timeout: whenever this many |
132 | seconds pass without a successful read or write on the underlying file |
155 | seconds pass without a successful read or write on the underlying file |
133 | handle, the C<on_timeout> callback will be invoked (and if that one is |
156 | handle, the C<on_timeout> callback will be invoked (and if that one is |
134 | missing, an C<ETIMEDOUT> error will be raised). |
157 | missing, a non-fatal C<ETIMEDOUT> error will be raised). |
135 | |
158 | |
136 | Note that timeout processing is also active when you currently do not have |
159 | Note that timeout processing is also active when you currently do not have |
137 | any outstanding read or write requests: If you plan to keep the connection |
160 | any outstanding read or write requests: If you plan to keep the connection |
138 | idle then you should disable the timout temporarily or ignore the timeout |
161 | idle then you should disable the timout temporarily or ignore the timeout |
139 | in the C<on_timeout> callback. |
162 | in the C<on_timeout> callback, in which case AnyEvent::Handle will simply |
|
|
163 | restart the timeout. |
140 | |
164 | |
141 | Zero (the default) disables this timeout. |
165 | Zero (the default) disables this timeout. |
142 | |
166 | |
143 | =item on_timeout => $cb->($handle) |
167 | =item on_timeout => $cb->($handle) |
144 | |
168 | |
… | |
… | |
148 | |
172 | |
149 | =item rbuf_max => <bytes> |
173 | =item rbuf_max => <bytes> |
150 | |
174 | |
151 | If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>) |
175 | If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>) |
152 | when the read buffer ever (strictly) exceeds this size. This is useful to |
176 | when the read buffer ever (strictly) exceeds this size. This is useful to |
153 | avoid denial-of-service attacks. |
177 | avoid some forms of denial-of-service attacks. |
154 | |
178 | |
155 | For example, a server accepting connections from untrusted sources should |
179 | For example, a server accepting connections from untrusted sources should |
156 | be configured to accept only so-and-so much data that it cannot act on |
180 | be configured to accept only so-and-so much data that it cannot act on |
157 | (for example, when expecting a line, an attacker could send an unlimited |
181 | (for example, when expecting a line, an attacker could send an unlimited |
158 | amount of data without a callback ever being called as long as the line |
182 | amount of data without a callback ever being called as long as the line |
159 | isn't finished). |
183 | isn't finished). |
160 | |
184 | |
|
|
185 | =item autocork => <boolean> |
|
|
186 | |
|
|
187 | When disabled (the default), then C<push_write> will try to immediately |
|
|
188 | write the data to the handle, if possible. This avoids having to register |
|
|
189 | a write watcher and wait for the next event loop iteration, but can |
|
|
190 | be inefficient if you write multiple small chunks (on the wire, this |
|
|
191 | disadvantage is usually avoided by your kernel's nagle algorithm, see |
|
|
192 | C<no_delay>, but this option can save costly syscalls). |
|
|
193 | |
|
|
194 | When enabled, then writes will always be queued till the next event loop |
|
|
195 | iteration. This is efficient when you do many small writes per iteration, |
|
|
196 | but less efficient when you do a single write only per iteration (or when |
|
|
197 | the write buffer often is full). It also increases write latency. |
|
|
198 | |
|
|
199 | =item no_delay => <boolean> |
|
|
200 | |
|
|
201 | When doing small writes on sockets, your operating system kernel might |
|
|
202 | wait a bit for more data before actually sending it out. This is called |
|
|
203 | the Nagle algorithm, and usually it is beneficial. |
|
|
204 | |
|
|
205 | In some situations you want as low a delay as possible, which can be |
|
|
206 | accomplishd by setting this option to a true value. |
|
|
207 | |
|
|
208 | The default is your opertaing system's default behaviour (most likely |
|
|
209 | enabled), this option explicitly enables or disables it, if possible. |
|
|
210 | |
161 | =item read_size => <bytes> |
211 | =item read_size => <bytes> |
162 | |
212 | |
163 | The default read block size (the amount of bytes this module will try to read |
213 | The default read block size (the amount of bytes this module will |
164 | during each (loop iteration). Default: C<8192>. |
214 | try to read during each loop iteration, which affects memory |
|
|
215 | requirements). Default: C<8192>. |
165 | |
216 | |
166 | =item low_water_mark => <bytes> |
217 | =item low_water_mark => <bytes> |
167 | |
218 | |
168 | Sets the amount of bytes (default: C<0>) that make up an "empty" write |
219 | Sets the amount of bytes (default: C<0>) that make up an "empty" write |
169 | buffer: If the write reaches this size or gets even samller it is |
220 | buffer: If the write reaches this size or gets even samller it is |
170 | considered empty. |
221 | considered empty. |
171 | |
222 | |
|
|
223 | Sometimes it can be beneficial (for performance reasons) to add data to |
|
|
224 | the write buffer before it is fully drained, but this is a rare case, as |
|
|
225 | the operating system kernel usually buffers data as well, so the default |
|
|
226 | is good in almost all cases. |
|
|
227 | |
172 | =item linger => <seconds> |
228 | =item linger => <seconds> |
173 | |
229 | |
174 | If non-zero (default: C<3600>), then the destructor of the |
230 | If non-zero (default: C<3600>), then the destructor of the |
175 | AnyEvent::Handle object will check wether there is still outstanding write |
231 | AnyEvent::Handle object will check whether there is still outstanding |
176 | data and will install a watcher that will write out this data. No errors |
232 | write data and will install a watcher that will write this data to the |
177 | will be reported (this mostly matches how the operating system treats |
233 | socket. No errors will be reported (this mostly matches how the operating |
178 | outstanding data at socket close time). |
234 | system treats outstanding data at socket close time). |
179 | |
235 | |
180 | This will not work for partial TLS data that could not yet been |
236 | This will not work for partial TLS data that could not be encoded |
181 | encoded. This data will be lost. |
237 | yet. This data will be lost. |
182 | |
238 | |
183 | =item tls => "accept" | "connect" | Net::SSLeay::SSL object |
239 | =item tls => "accept" | "connect" | Net::SSLeay::SSL object |
184 | |
240 | |
185 | When this parameter is given, it enables TLS (SSL) mode, that means it |
241 | When this parameter is given, it enables TLS (SSL) mode, that means |
186 | will start making tls handshake and will transparently encrypt/decrypt |
242 | AnyEvent will start a TLS handshake as soon as the conenction has been |
187 | data. |
243 | established and will transparently encrypt/decrypt data afterwards. |
188 | |
244 | |
189 | TLS mode requires Net::SSLeay to be installed (it will be loaded |
245 | TLS mode requires Net::SSLeay to be installed (it will be loaded |
190 | automatically when you try to create a TLS handle). |
246 | automatically when you try to create a TLS handle): this module doesn't |
|
|
247 | have a dependency on that module, so if your module requires it, you have |
|
|
248 | to add the dependency yourself. |
191 | |
249 | |
192 | For the TLS server side, use C<accept>, and for the TLS client side of a |
250 | Unlike TCP, TLS has a server and client side: for the TLS server side, use |
193 | connection, use C<connect> mode. |
251 | C<accept>, and for the TLS client side of a connection, use C<connect> |
|
|
252 | mode. |
194 | |
253 | |
195 | You can also provide your own TLS connection object, but you have |
254 | You can also provide your own TLS connection object, but you have |
196 | to make sure that you call either C<Net::SSLeay::set_connect_state> |
255 | to make sure that you call either C<Net::SSLeay::set_connect_state> |
197 | or C<Net::SSLeay::set_accept_state> on it before you pass it to |
256 | or C<Net::SSLeay::set_accept_state> on it before you pass it to |
198 | AnyEvent::Handle. |
257 | AnyEvent::Handle. |
199 | |
258 | |
200 | See the C<starttls> method if you need to start TLs negotiation later. |
259 | See the C<< ->starttls >> method for when need to start TLS negotiation later. |
201 | |
260 | |
202 | =item tls_ctx => $ssl_ctx |
261 | =item tls_ctx => $ssl_ctx |
203 | |
262 | |
204 | Use the given Net::SSLeay::CTX object to create the new TLS connection |
263 | Use the given C<Net::SSLeay::CTX> object to create the new TLS connection |
205 | (unless a connection object was specified directly). If this parameter is |
264 | (unless a connection object was specified directly). If this parameter is |
206 | missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. |
265 | missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. |
207 | |
266 | |
208 | =item json => JSON or JSON::XS object |
267 | =item json => JSON or JSON::XS object |
209 | |
268 | |
210 | This is the json coder object used by the C<json> read and write types. |
269 | This is the json coder object used by the C<json> read and write types. |
211 | |
270 | |
212 | If you don't supply it, then AnyEvent::Handle will create and use a |
271 | If you don't supply it, then AnyEvent::Handle will create and use a |
213 | suitable one, which will write and expect UTF-8 encoded JSON texts. |
272 | suitable one (on demand), which will write and expect UTF-8 encoded JSON |
|
|
273 | texts. |
214 | |
274 | |
215 | Note that you are responsible to depend on the JSON module if you want to |
275 | Note that you are responsible to depend on the JSON module if you want to |
216 | use this functionality, as AnyEvent does not have a dependency itself. |
276 | use this functionality, as AnyEvent does not have a dependency itself. |
217 | |
277 | |
218 | =item filter_r => $cb |
278 | =item filter_r => $cb |
219 | |
279 | |
220 | =item filter_w => $cb |
280 | =item filter_w => $cb |
221 | |
281 | |
222 | These exist, but are undocumented at this time. |
282 | These exist, but are undocumented at this time. (They are used internally |
|
|
283 | by the TLS code). |
223 | |
284 | |
224 | =back |
285 | =back |
225 | |
286 | |
226 | =cut |
287 | =cut |
227 | |
288 | |
… | |
… | |
240 | } |
301 | } |
241 | |
302 | |
242 | $self->{_activity} = AnyEvent->now; |
303 | $self->{_activity} = AnyEvent->now; |
243 | $self->_timeout; |
304 | $self->_timeout; |
244 | |
305 | |
245 | $self->on_drain (delete $self->{on_drain}) if $self->{on_drain}; |
306 | $self->on_drain (delete $self->{on_drain}) if exists $self->{on_drain}; |
|
|
307 | $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay}; |
246 | |
308 | |
247 | $self->start_read |
309 | $self->start_read |
248 | if $self->{on_read}; |
310 | if $self->{on_read}; |
249 | |
311 | |
250 | $self |
312 | $self |
… | |
… | |
257 | delete $self->{_rw}; |
319 | delete $self->{_rw}; |
258 | delete $self->{_ww}; |
320 | delete $self->{_ww}; |
259 | delete $self->{fh}; |
321 | delete $self->{fh}; |
260 | |
322 | |
261 | $self->stoptls; |
323 | $self->stoptls; |
|
|
324 | |
|
|
325 | delete $self->{on_read}; |
|
|
326 | delete $self->{_queue}; |
262 | } |
327 | } |
263 | |
328 | |
264 | sub _error { |
329 | sub _error { |
265 | my ($self, $errno, $fatal) = @_; |
330 | my ($self, $errno, $fatal) = @_; |
266 | |
331 | |
… | |
… | |
276 | } |
341 | } |
277 | } |
342 | } |
278 | |
343 | |
279 | =item $fh = $handle->fh |
344 | =item $fh = $handle->fh |
280 | |
345 | |
281 | This method returns the file handle of the L<AnyEvent::Handle> object. |
346 | This method returns the file handle used to create the L<AnyEvent::Handle> object. |
282 | |
347 | |
283 | =cut |
348 | =cut |
284 | |
349 | |
285 | sub fh { $_[0]{fh} } |
350 | sub fh { $_[0]{fh} } |
286 | |
351 | |
… | |
… | |
304 | $_[0]{on_eof} = $_[1]; |
369 | $_[0]{on_eof} = $_[1]; |
305 | } |
370 | } |
306 | |
371 | |
307 | =item $handle->on_timeout ($cb) |
372 | =item $handle->on_timeout ($cb) |
308 | |
373 | |
309 | Replace the current C<on_timeout> callback, or disables the callback |
374 | Replace the current C<on_timeout> callback, or disables the callback (but |
310 | (but not the timeout) if C<$cb> = C<undef>. See C<timeout> constructor |
375 | not the timeout) if C<$cb> = C<undef>. See the C<timeout> constructor |
311 | argument. |
376 | argument and method. |
312 | |
377 | |
313 | =cut |
378 | =cut |
314 | |
379 | |
315 | sub on_timeout { |
380 | sub on_timeout { |
316 | $_[0]{on_timeout} = $_[1]; |
381 | $_[0]{on_timeout} = $_[1]; |
|
|
382 | } |
|
|
383 | |
|
|
384 | =item $handle->autocork ($boolean) |
|
|
385 | |
|
|
386 | Enables or disables the current autocork behaviour (see C<autocork> |
|
|
387 | constructor argument). |
|
|
388 | |
|
|
389 | =cut |
|
|
390 | |
|
|
391 | =item $handle->no_delay ($boolean) |
|
|
392 | |
|
|
393 | Enables or disables the C<no_delay> setting (see constructor argument of |
|
|
394 | the same name for details). |
|
|
395 | |
|
|
396 | =cut |
|
|
397 | |
|
|
398 | sub no_delay { |
|
|
399 | $_[0]{no_delay} = $_[1]; |
|
|
400 | |
|
|
401 | eval { |
|
|
402 | local $SIG{__DIE__}; |
|
|
403 | setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1]; |
|
|
404 | }; |
317 | } |
405 | } |
318 | |
406 | |
319 | ############################################################################# |
407 | ############################################################################# |
320 | |
408 | |
321 | =item $handle->timeout ($seconds) |
409 | =item $handle->timeout ($seconds) |
… | |
… | |
436 | $self->_error ($!, 1); |
524 | $self->_error ($!, 1); |
437 | } |
525 | } |
438 | }; |
526 | }; |
439 | |
527 | |
440 | # try to write data immediately |
528 | # try to write data immediately |
441 | $cb->(); |
529 | $cb->() unless $self->{autocork}; |
442 | |
530 | |
443 | # if still data left in wbuf, we need to poll |
531 | # if still data left in wbuf, we need to poll |
444 | $self->{_ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb) |
532 | $self->{_ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb) |
445 | if length $self->{wbuf}; |
533 | if length $self->{wbuf}; |
446 | }; |
534 | }; |
… | |
… | |
593 | ways, the "simple" way, using only C<on_read> and the "complex" way, using |
681 | ways, the "simple" way, using only C<on_read> and the "complex" way, using |
594 | a queue. |
682 | a queue. |
595 | |
683 | |
596 | In the simple case, you just install an C<on_read> callback and whenever |
684 | In the simple case, you just install an C<on_read> callback and whenever |
597 | new data arrives, it will be called. You can then remove some data (if |
685 | new data arrives, it will be called. You can then remove some data (if |
598 | enough is there) from the read buffer (C<< $handle->rbuf >>) if you want |
686 | enough is there) from the read buffer (C<< $handle->rbuf >>). Or you cna |
599 | or not. |
687 | leave the data there if you want to accumulate more (e.g. when only a |
|
|
688 | partial message has been received so far). |
600 | |
689 | |
601 | In the more complex case, you want to queue multiple callbacks. In this |
690 | In the more complex case, you want to queue multiple callbacks. In this |
602 | case, AnyEvent::Handle will call the first queued callback each time new |
691 | case, AnyEvent::Handle will call the first queued callback each time new |
603 | data arrives (also the first time it is queued) and removes it when it has |
692 | data arrives (also the first time it is queued) and removes it when it has |
604 | done its job (see C<push_read>, below). |
693 | done its job (see C<push_read>, below). |
… | |
… | |
622 | # handle xml |
711 | # handle xml |
623 | }); |
712 | }); |
624 | }); |
713 | }); |
625 | }); |
714 | }); |
626 | |
715 | |
627 | Example 2: Implement a client for a protocol that replies either with |
716 | Example 2: Implement a client for a protocol that replies either with "OK" |
628 | "OK" and another line or "ERROR" for one request, and 64 bytes for the |
717 | and another line or "ERROR" for the first request that is sent, and 64 |
629 | second request. Due tot he availability of a full queue, we can just |
718 | bytes for the second request. Due to the availability of a queue, we can |
630 | pipeline sending both requests and manipulate the queue as necessary in |
719 | just pipeline sending both requests and manipulate the queue as necessary |
631 | the callbacks: |
720 | in the callbacks. |
632 | |
721 | |
633 | # request one |
722 | When the first callback is called and sees an "OK" response, it will |
|
|
723 | C<unshift> another line-read. This line-read will be queued I<before> the |
|
|
724 | 64-byte chunk callback. |
|
|
725 | |
|
|
726 | # request one, returns either "OK + extra line" or "ERROR" |
634 | $handle->push_write ("request 1\015\012"); |
727 | $handle->push_write ("request 1\015\012"); |
635 | |
728 | |
636 | # we expect "ERROR" or "OK" as response, so push a line read |
729 | # we expect "ERROR" or "OK" as response, so push a line read |
637 | $handle->push_read (line => sub { |
730 | $handle->push_read (line => sub { |
638 | # if we got an "OK", we have to _prepend_ another line, |
731 | # if we got an "OK", we have to _prepend_ another line, |
… | |
… | |
645 | ... |
738 | ... |
646 | }); |
739 | }); |
647 | } |
740 | } |
648 | }); |
741 | }); |
649 | |
742 | |
650 | # request two |
743 | # request two, simply returns 64 octets |
651 | $handle->push_write ("request 2\015\012"); |
744 | $handle->push_write ("request 2\015\012"); |
652 | |
745 | |
653 | # simply read 64 bytes, always |
746 | # simply read 64 bytes, always |
654 | $handle->push_read (chunk => 64, sub { |
747 | $handle->push_read (chunk => 64, sub { |
655 | my $response = $_[1]; |
748 | my $response = $_[1]; |
… | |
… | |
667 | |
760 | |
668 | if ( |
761 | if ( |
669 | defined $self->{rbuf_max} |
762 | defined $self->{rbuf_max} |
670 | && $self->{rbuf_max} < length $self->{rbuf} |
763 | && $self->{rbuf_max} < length $self->{rbuf} |
671 | ) { |
764 | ) { |
672 | return $self->_error (&Errno::ENOSPC, 1); |
765 | $self->_error (&Errno::ENOSPC, 1), return; |
673 | } |
766 | } |
674 | |
767 | |
675 | while () { |
768 | while () { |
676 | no strict 'refs'; |
|
|
677 | |
|
|
678 | my $len = length $self->{rbuf}; |
769 | my $len = length $self->{rbuf}; |
679 | |
770 | |
680 | if (my $cb = shift @{ $self->{_queue} }) { |
771 | if (my $cb = shift @{ $self->{_queue} }) { |
681 | unless ($cb->($self)) { |
772 | unless ($cb->($self)) { |
682 | if ($self->{_eof}) { |
773 | if ($self->{_eof}) { |
683 | # no progress can be made (not enough data and no data forthcoming) |
774 | # no progress can be made (not enough data and no data forthcoming) |
684 | $self->_error (&Errno::EPIPE, 1), last; |
775 | $self->_error (&Errno::EPIPE, 1), return; |
685 | } |
776 | } |
686 | |
777 | |
687 | unshift @{ $self->{_queue} }, $cb; |
778 | unshift @{ $self->{_queue} }, $cb; |
688 | last; |
779 | last; |
689 | } |
780 | } |
… | |
… | |
697 | && !@{ $self->{_queue} } # and the queue is still empty |
788 | && !@{ $self->{_queue} } # and the queue is still empty |
698 | && $self->{on_read} # but we still have on_read |
789 | && $self->{on_read} # but we still have on_read |
699 | ) { |
790 | ) { |
700 | # no further data will arrive |
791 | # no further data will arrive |
701 | # so no progress can be made |
792 | # so no progress can be made |
702 | $self->_error (&Errno::EPIPE, 1), last |
793 | $self->_error (&Errno::EPIPE, 1), return |
703 | if $self->{_eof}; |
794 | if $self->{_eof}; |
704 | |
795 | |
705 | last; # more data might arrive |
796 | last; # more data might arrive |
706 | } |
797 | } |
707 | } else { |
798 | } else { |
… | |
… | |
709 | delete $self->{_rw}; |
800 | delete $self->{_rw}; |
710 | last; |
801 | last; |
711 | } |
802 | } |
712 | } |
803 | } |
713 | |
804 | |
|
|
805 | if ($self->{_eof}) { |
|
|
806 | if ($self->{on_eof}) { |
714 | $self->{on_eof}($self) |
807 | $self->{on_eof}($self) |
715 | if $self->{_eof} && $self->{on_eof}; |
808 | } else { |
|
|
809 | $self->_error (0, 1); |
|
|
810 | } |
|
|
811 | } |
716 | |
812 | |
717 | # may need to restart read watcher |
813 | # may need to restart read watcher |
718 | unless ($self->{_rw}) { |
814 | unless ($self->{_rw}) { |
719 | $self->start_read |
815 | $self->start_read |
720 | if $self->{on_read} || @{ $self->{_queue} }; |
816 | if $self->{on_read} || @{ $self->{_queue} }; |
… | |
… | |
846 | $cb->($_[0], substr $_[0]{rbuf}, 0, $len, ""); |
942 | $cb->($_[0], substr $_[0]{rbuf}, 0, $len, ""); |
847 | 1 |
943 | 1 |
848 | } |
944 | } |
849 | }; |
945 | }; |
850 | |
946 | |
851 | # compatibility with older API |
|
|
852 | sub push_read_chunk { |
|
|
853 | $_[0]->push_read (chunk => $_[1], $_[2]); |
|
|
854 | } |
|
|
855 | |
|
|
856 | sub unshift_read_chunk { |
|
|
857 | $_[0]->unshift_read (chunk => $_[1], $_[2]); |
|
|
858 | } |
|
|
859 | |
|
|
860 | =item line => [$eol, ]$cb->($handle, $line, $eol) |
947 | =item line => [$eol, ]$cb->($handle, $line, $eol) |
861 | |
948 | |
862 | The callback will be called only once a full line (including the end of |
949 | The callback will be called only once a full line (including the end of |
863 | line marker, C<$eol>) has been read. This line (excluding the end of line |
950 | line marker, C<$eol>) has been read. This line (excluding the end of line |
864 | marker) will be passed to the callback as second argument (C<$line>), and |
951 | marker) will be passed to the callback as second argument (C<$line>), and |
… | |
… | |
879 | =cut |
966 | =cut |
880 | |
967 | |
881 | register_read_type line => sub { |
968 | register_read_type line => sub { |
882 | my ($self, $cb, $eol) = @_; |
969 | my ($self, $cb, $eol) = @_; |
883 | |
970 | |
884 | $eol = qr|(\015?\012)| if @_ < 3; |
971 | if (@_ < 3) { |
|
|
972 | # this is more than twice as fast as the generic code below |
|
|
973 | sub { |
|
|
974 | $_[0]{rbuf} =~ s/^([^\015\012]*)(\015?\012)// or return; |
|
|
975 | |
|
|
976 | $cb->($_[0], $1, $2); |
|
|
977 | 1 |
|
|
978 | } |
|
|
979 | } else { |
885 | $eol = quotemeta $eol unless ref $eol; |
980 | $eol = quotemeta $eol unless ref $eol; |
886 | $eol = qr|^(.*?)($eol)|s; |
981 | $eol = qr|^(.*?)($eol)|s; |
887 | |
982 | |
888 | sub { |
983 | sub { |
889 | $_[0]{rbuf} =~ s/$eol// or return; |
984 | $_[0]{rbuf} =~ s/$eol// or return; |
890 | |
985 | |
891 | $cb->($_[0], $1, $2); |
986 | $cb->($_[0], $1, $2); |
|
|
987 | 1 |
892 | 1 |
988 | } |
893 | } |
989 | } |
894 | }; |
990 | }; |
895 | |
|
|
896 | # compatibility with older API |
|
|
897 | sub push_read_line { |
|
|
898 | my $self = shift; |
|
|
899 | $self->push_read (line => @_); |
|
|
900 | } |
|
|
901 | |
|
|
902 | sub unshift_read_line { |
|
|
903 | my $self = shift; |
|
|
904 | $self->unshift_read (line => @_); |
|
|
905 | } |
|
|
906 | |
991 | |
907 | =item regex => $accept[, $reject[, $skip], $cb->($handle, $data) |
992 | =item regex => $accept[, $reject[, $skip], $cb->($handle, $data) |
908 | |
993 | |
909 | Makes a regex match against the regex object C<$accept> and returns |
994 | Makes a regex match against the regex object C<$accept> and returns |
910 | everything up to and including the match. |
995 | everything up to and including the match. |
… | |
… | |
1031 | register_read_type packstring => sub { |
1116 | register_read_type packstring => sub { |
1032 | my ($self, $cb, $format) = @_; |
1117 | my ($self, $cb, $format) = @_; |
1033 | |
1118 | |
1034 | sub { |
1119 | sub { |
1035 | # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method |
1120 | # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method |
1036 | defined (my $len = eval { unpack $format, $_[0]->{rbuf} }) |
1121 | defined (my $len = eval { unpack $format, $_[0]{rbuf} }) |
1037 | or return; |
1122 | or return; |
1038 | |
1123 | |
|
|
1124 | $format = length pack $format, $len; |
|
|
1125 | |
|
|
1126 | # bypass unshift if we already have the remaining chunk |
|
|
1127 | if ($format + $len <= length $_[0]{rbuf}) { |
|
|
1128 | my $data = substr $_[0]{rbuf}, $format, $len; |
|
|
1129 | substr $_[0]{rbuf}, 0, $format + $len, ""; |
|
|
1130 | $cb->($_[0], $data); |
|
|
1131 | } else { |
1039 | # remove prefix |
1132 | # remove prefix |
1040 | substr $_[0]->{rbuf}, 0, (length pack $format, $len), ""; |
1133 | substr $_[0]{rbuf}, 0, $format, ""; |
1041 | |
1134 | |
1042 | # read rest |
1135 | # read remaining chunk |
1043 | $_[0]->unshift_read (chunk => $len, $cb); |
1136 | $_[0]->unshift_read (chunk => $len, $cb); |
|
|
1137 | } |
1044 | |
1138 | |
1045 | 1 |
1139 | 1 |
1046 | } |
1140 | } |
1047 | }; |
1141 | }; |
1048 | |
1142 | |
… | |
… | |
1105 | |
1199 | |
1106 | require Storable; |
1200 | require Storable; |
1107 | |
1201 | |
1108 | sub { |
1202 | sub { |
1109 | # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method |
1203 | # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method |
1110 | defined (my $len = eval { unpack "w", $_[0]->{rbuf} }) |
1204 | defined (my $len = eval { unpack "w", $_[0]{rbuf} }) |
1111 | or return; |
1205 | or return; |
1112 | |
1206 | |
|
|
1207 | my $format = length pack "w", $len; |
|
|
1208 | |
|
|
1209 | # bypass unshift if we already have the remaining chunk |
|
|
1210 | if ($format + $len <= length $_[0]{rbuf}) { |
|
|
1211 | my $data = substr $_[0]{rbuf}, $format, $len; |
|
|
1212 | substr $_[0]{rbuf}, 0, $format + $len, ""; |
|
|
1213 | $cb->($_[0], Storable::thaw ($data)); |
|
|
1214 | } else { |
1113 | # remove prefix |
1215 | # remove prefix |
1114 | substr $_[0]->{rbuf}, 0, (length pack "w", $len), ""; |
1216 | substr $_[0]{rbuf}, 0, $format, ""; |
1115 | |
1217 | |
1116 | # read rest |
1218 | # read remaining chunk |
1117 | $_[0]->unshift_read (chunk => $len, sub { |
1219 | $_[0]->unshift_read (chunk => $len, sub { |
1118 | if (my $ref = eval { Storable::thaw ($_[1]) }) { |
1220 | if (my $ref = eval { Storable::thaw ($_[1]) }) { |
1119 | $cb->($_[0], $ref); |
1221 | $cb->($_[0], $ref); |
1120 | } else { |
1222 | } else { |
1121 | $self->_error (&Errno::EBADMSG); |
1223 | $self->_error (&Errno::EBADMSG); |
|
|
1224 | } |
1122 | } |
1225 | }); |
1123 | }); |
1226 | } |
|
|
1227 | |
|
|
1228 | 1 |
1124 | } |
1229 | } |
1125 | }; |
1230 | }; |
1126 | |
1231 | |
1127 | =back |
1232 | =back |
1128 | |
1233 | |
… | |
… | |
1274 | # basically, this is deep magic (because SSL_read should have the same issues) |
1379 | # basically, this is deep magic (because SSL_read should have the same issues) |
1275 | # but the openssl maintainers basically said: "trust us, it just works". |
1380 | # but the openssl maintainers basically said: "trust us, it just works". |
1276 | # (unfortunately, we have to hardcode constants because the abysmally misdesigned |
1381 | # (unfortunately, we have to hardcode constants because the abysmally misdesigned |
1277 | # and mismaintained ssleay-module doesn't even offer them). |
1382 | # and mismaintained ssleay-module doesn't even offer them). |
1278 | # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html |
1383 | # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html |
|
|
1384 | # |
|
|
1385 | # in short: this is a mess. |
|
|
1386 | # |
|
|
1387 | # note that we do not try to kepe the length constant between writes as we are required to do. |
|
|
1388 | # we assume that most (but not all) of this insanity only applies to non-blocking cases, |
|
|
1389 | # and we drive openssl fully in blocking mode here. |
1279 | Net::SSLeay::CTX_set_mode ($self->{tls}, |
1390 | Net::SSLeay::CTX_set_mode ($self->{tls}, |
1280 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) |
1391 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) |
1281 | | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); |
1392 | | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); |
1282 | |
1393 | |
1283 | $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
1394 | $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); |
… | |
… | |
1389 | =over 4 |
1500 | =over 4 |
1390 | |
1501 | |
1391 | =item * all constructor arguments become object members. |
1502 | =item * all constructor arguments become object members. |
1392 | |
1503 | |
1393 | At least initially, when you pass a C<tls>-argument to the constructor it |
1504 | At least initially, when you pass a C<tls>-argument to the constructor it |
1394 | will end up in C<< $handle->{tls} >>. Those members might be changes or |
1505 | will end up in C<< $handle->{tls} >>. Those members might be changed or |
1395 | mutated later on (for example C<tls> will hold the TLS connection object). |
1506 | mutated later on (for example C<tls> will hold the TLS connection object). |
1396 | |
1507 | |
1397 | =item * other object member names are prefixed with an C<_>. |
1508 | =item * other object member names are prefixed with an C<_>. |
1398 | |
1509 | |
1399 | All object members not explicitly documented (internal use) are prefixed |
1510 | All object members not explicitly documented (internal use) are prefixed |