ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent/lib/AnyEvent/Handle.pm
(Generate patch)

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents):
Revision 1.87 by root, Thu Aug 21 20:52:39 2008 UTC vs.
Revision 1.145 by root, Mon Jul 6 21:47:14 2009 UTC

14 14
15AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent 15AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent
16 16
17=cut 17=cut
18 18
19our $VERSION = 4.232; 19our $VERSION = 4.8;
20 20
21=head1 SYNOPSIS 21=head1 SYNOPSIS
22 22
23 use AnyEvent; 23 use AnyEvent;
24 use AnyEvent::Handle; 24 use AnyEvent::Handle;
27 27
28 my $handle = 28 my $handle =
29 AnyEvent::Handle->new ( 29 AnyEvent::Handle->new (
30 fh => \*STDIN, 30 fh => \*STDIN,
31 on_eof => sub { 31 on_eof => sub {
32 $cv->broadcast; 32 $cv->send;
33 }, 33 },
34 ); 34 );
35 35
36 # send some request line 36 # send some request line
37 $handle->push_write ("getinfo\015\012"); 37 $handle->push_write ("getinfo\015\012");
63 63
64=head1 METHODS 64=head1 METHODS
65 65
66=over 4 66=over 4
67 67
68=item B<new (%args)> 68=item $handle = B<new> AnyEvent::TLS fh => $filehandle, key => value...
69 69
70The constructor supports these arguments (all as key => value pairs). 70The constructor supports these arguments (all as C<< key => value >> pairs).
71 71
72=over 4 72=over 4
73 73
74=item fh => $filehandle [MANDATORY] 74=item fh => $filehandle [MANDATORY]
75 75
84Set the callback to be called when an end-of-file condition is detected, 84Set the callback to be called when an end-of-file condition is detected,
85i.e. in the case of a socket, when the other side has closed the 85i.e. in the case of a socket, when the other side has closed the
86connection cleanly. 86connection cleanly.
87 87
88For sockets, this just means that the other side has stopped sending data, 88For sockets, this just means that the other side has stopped sending data,
89you can still try to write data, and, in fact, one can return from the eof 89you can still try to write data, and, in fact, one can return from the EOF
90callback and continue writing data, as only the read part has been shut 90callback and continue writing data, as only the read part has been shut
91down. 91down.
92 92
93While not mandatory, it is I<highly> recommended to set an eof callback, 93While not mandatory, it is I<highly> recommended to set an EOF callback,
94otherwise you might end up with a closed socket while you are still 94otherwise you might end up with a closed socket while you are still
95waiting for data. 95waiting for data.
96 96
97If an EOF condition has been detected but no C<on_eof> callback has been 97If an EOF condition has been detected but no C<on_eof> callback has been
98set, then a fatal error will be raised with C<$!> set to <0>. 98set, then a fatal error will be raised with C<$!> set to <0>.
99 99
100=item on_error => $cb->($handle, $fatal) 100=item on_error => $cb->($handle, $fatal, $message)
101 101
102This is the error callback, which is called when, well, some error 102This is the error callback, which is called when, well, some error
103occured, such as not being able to resolve the hostname, failure to 103occured, such as not being able to resolve the hostname, failure to
104connect or a read error. 104connect or a read error.
105 105
106Some errors are fatal (which is indicated by C<$fatal> being true). On 106Some errors are fatal (which is indicated by C<$fatal> being true). On
107fatal errors the handle object will be shut down and will not be usable 107fatal 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 108(but you are free to look at the current C<< ->rbuf >>). Examples of fatal
109errors are an EOF condition with active (but unsatisifable) read watchers 109errors are an EOF condition with active (but unsatisifable) read watchers
110(C<EPIPE>) or I/O errors. 110(C<EPIPE>) or I/O errors.
111
112AnyEvent::Handle tries to find an appropriate error code for you to check
113against, but in some cases (TLS errors), this does not work well. It is
114recommended to always output the C<$message> argument in human-readable
115error messages (it's usually the same as C<"$!">).
111 116
112Non-fatal errors can be retried by simply returning, but it is recommended 117Non-fatal errors can be retried by simply returning, but it is recommended
113to simply ignore this parameter and instead abondon the handle object 118to simply ignore this parameter and instead abondon the handle object
114when this callback is invoked. Examples of non-fatal errors are timeouts 119when this callback is invoked. Examples of non-fatal errors are timeouts
115C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>). 120C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
116 121
117On callback entrance, the value of C<$!> contains the operating system 122On callback entrance, the value of C<$!> contains the operating system
118error (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT> or C<EBADMSG>). 123error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
124C<EPROTO>).
119 125
120While not mandatory, it is I<highly> recommended to set this callback, as 126While not mandatory, it is I<highly> recommended to set this callback, as
121you will not be notified of errors otherwise. The default simply calls 127you will not be notified of errors otherwise. The default simply calls
122C<croak>. 128C<croak>.
123 129
127and no read request is in the queue (unlike read queue callbacks, this 133and no read request is in the queue (unlike read queue callbacks, this
128callback will only be called when at least one octet of data is in the 134callback will only be called when at least one octet of data is in the
129read buffer). 135read buffer).
130 136
131To access (and remove data from) the read buffer, use the C<< ->rbuf >> 137To access (and remove data from) the read buffer, use the C<< ->rbuf >>
132method or access the C<$handle->{rbuf}> member directly. 138method or access the C<< $handle->{rbuf} >> member directly. Note that you
139must not enlarge or modify the read buffer, you can only remove data at
140the beginning from it.
133 141
134When an EOF condition is detected then AnyEvent::Handle will first try to 142When an EOF condition is detected then AnyEvent::Handle will first try to
135feed all the remaining data to the queued callbacks and C<on_read> before 143feed all the remaining data to the queued callbacks and C<on_read> before
136calling the C<on_eof> callback. If no progress can be made, then a fatal 144calling the C<on_eof> callback. If no progress can be made, then a fatal
137error will be raised (with C<$!> set to C<EPIPE>). 145error will be raised (with C<$!> set to C<EPIPE>).
152=item timeout => $fractional_seconds 160=item timeout => $fractional_seconds
153 161
154If non-zero, then this enables an "inactivity" timeout: whenever this many 162If non-zero, then this enables an "inactivity" timeout: whenever this many
155seconds pass without a successful read or write on the underlying file 163seconds pass without a successful read or write on the underlying file
156handle, the C<on_timeout> callback will be invoked (and if that one is 164handle, the C<on_timeout> callback will be invoked (and if that one is
157missing, an C<ETIMEDOUT> error will be raised). 165missing, a non-fatal C<ETIMEDOUT> error will be raised).
158 166
159Note that timeout processing is also active when you currently do not have 167Note that timeout processing is also active when you currently do not have
160any outstanding read or write requests: If you plan to keep the connection 168any outstanding read or write requests: If you plan to keep the connection
161idle then you should disable the timout temporarily or ignore the timeout 169idle then you should disable the timout temporarily or ignore the timeout
162in the C<on_timeout> callback. 170in the C<on_timeout> callback, in which case AnyEvent::Handle will simply
171restart the timeout.
163 172
164Zero (the default) disables this timeout. 173Zero (the default) disables this timeout.
165 174
166=item on_timeout => $cb->($handle) 175=item on_timeout => $cb->($handle)
167 176
171 180
172=item rbuf_max => <bytes> 181=item rbuf_max => <bytes>
173 182
174If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>) 183If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>)
175when the read buffer ever (strictly) exceeds this size. This is useful to 184when the read buffer ever (strictly) exceeds this size. This is useful to
176avoid denial-of-service attacks. 185avoid some forms of denial-of-service attacks.
177 186
178For example, a server accepting connections from untrusted sources should 187For example, a server accepting connections from untrusted sources should
179be configured to accept only so-and-so much data that it cannot act on 188be configured to accept only so-and-so much data that it cannot act on
180(for example, when expecting a line, an attacker could send an unlimited 189(for example, when expecting a line, an attacker could send an unlimited
181amount of data without a callback ever being called as long as the line 190amount of data without a callback ever being called as long as the line
182isn't finished). 191isn't finished).
183 192
184=item autocork => <boolean> 193=item autocork => <boolean>
185 194
186When disabled (the default), then C<push_write> will try to immediately 195When disabled (the default), then C<push_write> will try to immediately
187write the data to the handle if possible. This avoids having to register 196write the data to the handle, if possible. This avoids having to register
188a write watcher and wait for the next event loop iteration, but can be 197a write watcher and wait for the next event loop iteration, but can
189inefficient if you write multiple small chunks (this disadvantage is 198be inefficient if you write multiple small chunks (on the wire, this
190usually avoided by your kernel's nagle algorithm, see C<low_delay>). 199disadvantage is usually avoided by your kernel's nagle algorithm, see
200C<no_delay>, but this option can save costly syscalls).
191 201
192When enabled, then writes will always be queued till the next event loop 202When enabled, then writes will always be queued till the next event loop
193iteration. This is efficient when you do many small writes per iteration, 203iteration. This is efficient when you do many small writes per iteration,
194but less efficient when you do a single write only. 204but less efficient when you do a single write only per iteration (or when
205the write buffer often is full). It also increases write latency.
195 206
196=item no_delay => <boolean> 207=item no_delay => <boolean>
197 208
198When doing small writes on sockets, your operating system kernel might 209When doing small writes on sockets, your operating system kernel might
199wait a bit for more data before actually sending it out. This is called 210wait a bit for more data before actually sending it out. This is called
200the Nagle algorithm, and usually it is beneficial. 211the Nagle algorithm, and usually it is beneficial.
201 212
202In some situations you want as low a delay as possible, which cna be 213In some situations you want as low a delay as possible, which can be
203accomplishd by setting this option to true. 214accomplishd by setting this option to a true value.
204 215
205The default is your opertaing system's default behaviour, this option 216The default is your opertaing system's default behaviour (most likely
206explicitly enables or disables it, if possible. 217enabled), this option explicitly enables or disables it, if possible.
207 218
208=item read_size => <bytes> 219=item read_size => <bytes>
209 220
210The default read block size (the amount of bytes this module will try to read 221The default read block size (the amount of bytes this module will
211during each (loop iteration). Default: C<8192>. 222try to read during each loop iteration, which affects memory
223requirements). Default: C<8192>.
212 224
213=item low_water_mark => <bytes> 225=item low_water_mark => <bytes>
214 226
215Sets the amount of bytes (default: C<0>) that make up an "empty" write 227Sets the amount of bytes (default: C<0>) that make up an "empty" write
216buffer: If the write reaches this size or gets even samller it is 228buffer: If the write reaches this size or gets even samller it is
217considered empty. 229considered empty.
218 230
231Sometimes it can be beneficial (for performance reasons) to add data to
232the write buffer before it is fully drained, but this is a rare case, as
233the operating system kernel usually buffers data as well, so the default
234is good in almost all cases.
235
219=item linger => <seconds> 236=item linger => <seconds>
220 237
221If non-zero (default: C<3600>), then the destructor of the 238If non-zero (default: C<3600>), then the destructor of the
222AnyEvent::Handle object will check wether there is still outstanding write 239AnyEvent::Handle object will check whether there is still outstanding
223data and will install a watcher that will write out this data. No errors 240write data and will install a watcher that will write this data to the
224will be reported (this mostly matches how the operating system treats 241socket. No errors will be reported (this mostly matches how the operating
225outstanding data at socket close time). 242system treats outstanding data at socket close time).
226 243
227This will not work for partial TLS data that could not yet been 244This will not work for partial TLS data that could not be encoded
228encoded. This data will be lost. 245yet. This data will be lost. Calling the C<stoptls> method in time might
246help.
247
248=item peername => $string
249
250A string used to identify the remote site - usually the DNS hostname
251(I<not> IDN!) used to create the connection, rarely the IP address.
252
253Apart from being useful in error messages, this string is also used in TLS
254peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This
255verification will be skipped when C<peername> is not specified or
256C<undef>.
229 257
230=item tls => "accept" | "connect" | Net::SSLeay::SSL object 258=item tls => "accept" | "connect" | Net::SSLeay::SSL object
231 259
232When this parameter is given, it enables TLS (SSL) mode, that means 260When this parameter is given, it enables TLS (SSL) mode, that means
233AnyEvent will start a TLS handshake and will transparently encrypt/decrypt 261AnyEvent will start a TLS handshake as soon as the conenction has been
234data. 262established and will transparently encrypt/decrypt data afterwards.
263
264All TLS protocol errors will be signalled as C<EPROTO>, with an
265appropriate error message.
235 266
236TLS mode requires Net::SSLeay to be installed (it will be loaded 267TLS mode requires Net::SSLeay to be installed (it will be loaded
237automatically when you try to create a TLS handle). 268automatically when you try to create a TLS handle): this module doesn't
269have a dependency on that module, so if your module requires it, you have
270to add the dependency yourself.
238 271
239Unlike TCP, TLS has a server and client side: for the TLS server side, use 272Unlike TCP, TLS has a server and client side: for the TLS server side, use
240C<accept>, and for the TLS client side of a connection, use C<connect> 273C<accept>, and for the TLS client side of a connection, use C<connect>
241mode. 274mode.
242 275
243You can also provide your own TLS connection object, but you have 276You can also provide your own TLS connection object, but you have
244to make sure that you call either C<Net::SSLeay::set_connect_state> 277to make sure that you call either C<Net::SSLeay::set_connect_state>
245or C<Net::SSLeay::set_accept_state> on it before you pass it to 278or C<Net::SSLeay::set_accept_state> on it before you pass it to
246AnyEvent::Handle. 279AnyEvent::Handle. Also, this module will take ownership of this connection
280object.
247 281
282At some future point, AnyEvent::Handle might switch to another TLS
283implementation, then the option to use your own session object will go
284away.
285
286B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
287passing in the wrong integer will lead to certain crash. This most often
288happens when one uses a stylish C<< tls => 1 >> and is surprised about the
289segmentation fault.
290
248See the C<starttls> method for when need to start TLS negotiation later. 291See the C<< ->starttls >> method for when need to start TLS negotiation later.
249 292
250=item tls_ctx => $ssl_ctx 293=item tls_ctx => $anyevent_tls
251 294
252Use the given Net::SSLeay::CTX object to create the new TLS connection 295Use the given C<AnyEvent::TLS> object to create the new TLS connection
253(unless a connection object was specified directly). If this parameter is 296(unless a connection object was specified directly). If this parameter is
254missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. 297missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>.
298
299Instead of an object, you can also specify a hash reference with C<< key
300=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a
301new TLS context object.
302
303=item on_starttls => $cb->($handle, $success[, $error_message])
304
305This callback will be invoked when the TLS/SSL handshake has finished. If
306C<$success> is true, then the TLS handshake succeeded, otherwise it failed
307(C<on_stoptls> will not be called in this case).
308
309The session in C<< $handle->{tls} >> can still be examined in this
310callback, even when the handshake was not successful.
311
312TLS handshake failures will not cause C<on_error> to be invoked when this
313callback is in effect, instead, the error message will be passed to C<on_starttls>.
314
315Without this callback, handshake failures lead to C<on_error> being
316called, as normal.
317
318Note that you cannot call C<starttls> right again in this callback. If you
319need to do that, start an zero-second timer instead whose callback can
320then call C<< ->starttls >> again.
321
322=item on_stoptls => $cb->($handle)
323
324When a SSLv3/TLS shutdown/close notify/EOF is detected and this callback is
325set, then it will be invoked after freeing the TLS session. If it is not,
326then a TLS shutdown condition will be treated like a normal EOF condition
327on the handle.
328
329The session in C<< $handle->{tls} >> can still be examined in this
330callback.
331
332This callback will only be called on TLS shutdowns, not when the
333underlying handle signals EOF.
255 334
256=item json => JSON or JSON::XS object 335=item json => JSON or JSON::XS object
257 336
258This is the json coder object used by the C<json> read and write types. 337This is the json coder object used by the C<json> read and write types.
259 338
262texts. 341texts.
263 342
264Note that you are responsible to depend on the JSON module if you want to 343Note that you are responsible to depend on the JSON module if you want to
265use this functionality, as AnyEvent does not have a dependency itself. 344use this functionality, as AnyEvent does not have a dependency itself.
266 345
267=item filter_r => $cb
268
269=item filter_w => $cb
270
271These exist, but are undocumented at this time. (They are used internally
272by the TLS code).
273
274=back 346=back
275 347
276=cut 348=cut
277 349
278sub new { 350sub new {
279 my $class = shift; 351 my $class = shift;
280
281 my $self = bless { @_ }, $class; 352 my $self = bless { @_ }, $class;
282 353
283 $self->{fh} or Carp::croak "mandatory argument fh is missing"; 354 $self->{fh} or Carp::croak "mandatory argument fh is missing";
284 355
285 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 356 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
286
287 if ($self->{tls}) {
288 require Net::SSLeay;
289 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx});
290 }
291 357
292 $self->{_activity} = AnyEvent->now; 358 $self->{_activity} = AnyEvent->now;
293 $self->_timeout; 359 $self->_timeout;
294 360
295 $self->on_drain (delete $self->{on_drain}) if exists $self->{on_drain};
296 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay}; 361 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay};
362
363 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
364 if $self->{tls};
365
366 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain};
297 367
298 $self->start_read 368 $self->start_read
299 if $self->{on_read}; 369 if $self->{on_read};
300 370
301 $self 371 $self->{fh} && $self
302} 372}
303 373
304sub _shutdown { 374sub _shutdown {
305 my ($self) = @_; 375 my ($self) = @_;
306 376
307 delete $self->{_tw}; 377 delete @$self{qw(_tw _rw _ww fh wbuf on_read _queue)};
308 delete $self->{_rw}; 378 $self->{_eof} = 1; # tell starttls et. al to stop trying
309 delete $self->{_ww};
310 delete $self->{fh};
311 379
312 $self->stoptls; 380 &_freetls;
313
314 delete $self->{on_read};
315 delete $self->{_queue};
316} 381}
317 382
318sub _error { 383sub _error {
319 my ($self, $errno, $fatal) = @_; 384 my ($self, $errno, $fatal, $message) = @_;
320 385
321 $self->_shutdown 386 $self->_shutdown
322 if $fatal; 387 if $fatal;
323 388
324 $! = $errno; 389 $! = $errno;
390 $message ||= "$!";
325 391
326 if ($self->{on_error}) { 392 if ($self->{on_error}) {
327 $self->{on_error}($self, $fatal); 393 $self->{on_error}($self, $fatal, $message);
328 } else { 394 } elsif ($self->{fh}) {
329 Carp::croak "AnyEvent::Handle uncaught error: $!"; 395 Carp::croak "AnyEvent::Handle uncaught error: $message";
330 } 396 }
331} 397}
332 398
333=item $fh = $handle->fh 399=item $fh = $handle->fh
334 400
335This method returns the file handle of the L<AnyEvent::Handle> object. 401This method returns the file handle used to create the L<AnyEvent::Handle> object.
336 402
337=cut 403=cut
338 404
339sub fh { $_[0]{fh} } 405sub fh { $_[0]{fh} }
340 406
358 $_[0]{on_eof} = $_[1]; 424 $_[0]{on_eof} = $_[1];
359} 425}
360 426
361=item $handle->on_timeout ($cb) 427=item $handle->on_timeout ($cb)
362 428
363Replace the current C<on_timeout> callback, or disables the callback 429Replace the current C<on_timeout> callback, or disables the callback (but
364(but not the timeout) if C<$cb> = C<undef>. See C<timeout> constructor 430not the timeout) if C<$cb> = C<undef>. See the C<timeout> constructor
365argument. 431argument and method.
366 432
367=cut 433=cut
368 434
369sub on_timeout { 435sub on_timeout {
370 $_[0]{on_timeout} = $_[1]; 436 $_[0]{on_timeout} = $_[1];
371} 437}
372 438
373=item $handle->autocork ($boolean) 439=item $handle->autocork ($boolean)
374 440
375Enables or disables the current autocork behaviour (see C<autocork> 441Enables or disables the current autocork behaviour (see C<autocork>
376constructor argument). 442constructor argument). Changes will only take effect on the next write.
377 443
378=cut 444=cut
445
446sub autocork {
447 $_[0]{autocork} = $_[1];
448}
379 449
380=item $handle->no_delay ($boolean) 450=item $handle->no_delay ($boolean)
381 451
382Enables or disables the C<no_delay> setting (see constructor argument of 452Enables or disables the C<no_delay> setting (see constructor argument of
383the same name for details). 453the same name for details).
389 459
390 eval { 460 eval {
391 local $SIG{__DIE__}; 461 local $SIG{__DIE__};
392 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1]; 462 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1];
393 }; 463 };
464}
465
466=item $handle->on_starttls ($cb)
467
468Replace the current C<on_starttls> callback (see the C<on_starttls> constructor argument).
469
470=cut
471
472sub on_starttls {
473 $_[0]{on_starttls} = $_[1];
474}
475
476=item $handle->on_stoptls ($cb)
477
478Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument).
479
480=cut
481
482sub on_starttls {
483 $_[0]{on_stoptls} = $_[1];
394} 484}
395 485
396############################################################################# 486#############################################################################
397 487
398=item $handle->timeout ($seconds) 488=item $handle->timeout ($seconds)
476 my ($self, $cb) = @_; 566 my ($self, $cb) = @_;
477 567
478 $self->{on_drain} = $cb; 568 $self->{on_drain} = $cb;
479 569
480 $cb->($self) 570 $cb->($self)
481 if $cb && $self->{low_water_mark} >= length $self->{wbuf}; 571 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
482} 572}
483 573
484=item $handle->push_write ($data) 574=item $handle->push_write ($data)
485 575
486Queues the given scalar to be written. You can push as much data as you 576Queues the given scalar to be written. You can push as much data as you
503 substr $self->{wbuf}, 0, $len, ""; 593 substr $self->{wbuf}, 0, $len, "";
504 594
505 $self->{_activity} = AnyEvent->now; 595 $self->{_activity} = AnyEvent->now;
506 596
507 $self->{on_drain}($self) 597 $self->{on_drain}($self)
508 if $self->{low_water_mark} >= length $self->{wbuf} 598 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
509 && $self->{on_drain}; 599 && $self->{on_drain};
510 600
511 delete $self->{_ww} unless length $self->{wbuf}; 601 delete $self->{_ww} unless length $self->{wbuf};
512 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 602 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
513 $self->_error ($!, 1); 603 $self->_error ($!, 1);
537 627
538 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") 628 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write")
539 ->($self, @_); 629 ->($self, @_);
540 } 630 }
541 631
542 if ($self->{filter_w}) { 632 if ($self->{tls}) {
543 $self->{filter_w}($self, \$_[0]); 633 $self->{_tls_wbuf} .= $_[0];
634
635 &_dotls ($self);
544 } else { 636 } else {
545 $self->{wbuf} .= $_[0]; 637 $self->{wbuf} .= $_[0];
546 $self->_drain_wbuf; 638 $self->_drain_wbuf;
547 } 639 }
548} 640}
565=cut 657=cut
566 658
567register_write_type netstring => sub { 659register_write_type netstring => sub {
568 my ($self, $string) = @_; 660 my ($self, $string) = @_;
569 661
570 sprintf "%d:%s,", (length $string), $string 662 (length $string) . ":$string,"
571}; 663};
572 664
573=item packstring => $format, $data 665=item packstring => $format, $data
574 666
575An octet string prefixed with an encoded length. The encoding C<$format> 667An octet string prefixed with an encoded length. The encoding C<$format>
640 732
641 pack "w/a*", Storable::nfreeze ($ref) 733 pack "w/a*", Storable::nfreeze ($ref)
642}; 734};
643 735
644=back 736=back
737
738=item $handle->push_shutdown
739
740Sometimes you know you want to close the socket after writing your data
741before it was actually written. One way to do that is to replace your
742C<on_drain> handler by a callback that shuts down the socket (and set
743C<low_water_mark> to C<0>). This method is a shorthand for just that, and
744replaces the C<on_drain> callback with:
745
746 sub { shutdown $_[0]{fh}, 1 } # for push_shutdown
747
748This simply shuts down the write side and signals an EOF condition to the
749the peer.
750
751You can rely on the normal read queue and C<on_eof> handling
752afterwards. This is the cleanest way to close a connection.
753
754=cut
755
756sub push_shutdown {
757 my ($self) = @_;
758
759 delete $self->{low_water_mark};
760 $self->on_drain (sub { shutdown $_[0]{fh}, 1 });
761}
645 762
646=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args) 763=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args)
647 764
648This function (not method) lets you add your own types to C<push_write>. 765This function (not method) lets you add your own types to C<push_write>.
649Whenever the given C<type> is used, C<push_write> will invoke the code 766Whenever the given C<type> is used, C<push_write> will invoke the code
753 ) { 870 ) {
754 $self->_error (&Errno::ENOSPC, 1), return; 871 $self->_error (&Errno::ENOSPC, 1), return;
755 } 872 }
756 873
757 while () { 874 while () {
875 # we need to use a separate tls read buffer, as we must not receive data while
876 # we are draining the buffer, and this can only happen with TLS.
877 $self->{rbuf} .= delete $self->{_tls_rbuf} if exists $self->{_tls_rbuf};
878
758 my $len = length $self->{rbuf}; 879 my $len = length $self->{rbuf};
759 880
760 if (my $cb = shift @{ $self->{_queue} }) { 881 if (my $cb = shift @{ $self->{_queue} }) {
761 unless ($cb->($self)) { 882 unless ($cb->($self)) {
762 if ($self->{_eof}) { 883 if ($self->{_eof}) {
784 905
785 last; # more data might arrive 906 last; # more data might arrive
786 } 907 }
787 } else { 908 } else {
788 # read side becomes idle 909 # read side becomes idle
789 delete $self->{_rw}; 910 delete $self->{_rw} unless $self->{tls};
790 last; 911 last;
791 } 912 }
792 } 913 }
793 914
794 if ($self->{_eof}) { 915 if ($self->{_eof}) {
795 if ($self->{on_eof}) { 916 if ($self->{on_eof}) {
796 $self->{on_eof}($self) 917 $self->{on_eof}($self)
797 } else { 918 } else {
798 $self->_error (0, 1); 919 $self->_error (0, 1, "Unexpected end-of-file");
799 } 920 }
800 } 921 }
801 922
802 # may need to restart read watcher 923 # may need to restart read watcher
803 unless ($self->{_rw}) { 924 unless ($self->{_rw}) {
823 944
824=item $handle->rbuf 945=item $handle->rbuf
825 946
826Returns the read buffer (as a modifiable lvalue). 947Returns the read buffer (as a modifiable lvalue).
827 948
828You can access the read buffer directly as the C<< ->{rbuf} >> member, if 949You can access the read buffer directly as the C<< ->{rbuf} >>
829you want. 950member, if you want. However, the only operation allowed on the
951read buffer (apart from looking at it) is removing data from its
952beginning. Otherwise modifying or appending to it is not allowed and will
953lead to hard-to-track-down bugs.
830 954
831NOTE: The read buffer should only be used or modified if the C<on_read>, 955NOTE: The read buffer should only be used or modified if the C<on_read>,
832C<push_read> or C<unshift_read> methods are used. The other read methods 956C<push_read> or C<unshift_read> methods are used. The other read methods
833automatically manage the read buffer. 957automatically manage the read buffer.
834 958
1089An octet string prefixed with an encoded length. The encoding C<$format> 1213An octet string prefixed with an encoded length. The encoding C<$format>
1090uses the same format as a Perl C<pack> format, but must specify a single 1214uses the same format as a Perl C<pack> format, but must specify a single
1091integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an 1215integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an
1092optional C<!>, C<< < >> or C<< > >> modifier). 1216optional C<!>, C<< < >> or C<< > >> modifier).
1093 1217
1094DNS over TCP uses a prefix of C<n>, EPP uses a prefix of C<N>. 1218For example, DNS over TCP uses a prefix of C<n> (2 octet network order),
1219EPP uses a prefix of C<N> (4 octtes).
1095 1220
1096Example: read a block of data prefixed by its length in BER-encoded 1221Example: read a block of data prefixed by its length in BER-encoded
1097format (very efficient). 1222format (very efficient).
1098 1223
1099 $handle->push_read (packstring => "w", sub { 1224 $handle->push_read (packstring => "w", sub {
1129 } 1254 }
1130}; 1255};
1131 1256
1132=item json => $cb->($handle, $hash_or_arrayref) 1257=item json => $cb->($handle, $hash_or_arrayref)
1133 1258
1134Reads a JSON object or array, decodes it and passes it to the callback. 1259Reads a JSON object or array, decodes it and passes it to the
1260callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1135 1261
1136If a C<json> object was passed to the constructor, then that will be used 1262If a C<json> object was passed to the constructor, then that will be used
1137for the final decode, otherwise it will create a JSON coder expecting UTF-8. 1263for the final decode, otherwise it will create a JSON coder expecting UTF-8.
1138 1264
1139This read type uses the incremental parser available with JSON version 1265This read type uses the incremental parser available with JSON version
1148=cut 1274=cut
1149 1275
1150register_read_type json => sub { 1276register_read_type json => sub {
1151 my ($self, $cb) = @_; 1277 my ($self, $cb) = @_;
1152 1278
1153 require JSON; 1279 my $json = $self->{json} ||=
1280 eval { require JSON::XS; JSON::XS->new->utf8 }
1281 || do { require JSON; JSON->new->utf8 };
1154 1282
1155 my $data; 1283 my $data;
1156 my $rbuf = \$self->{rbuf}; 1284 my $rbuf = \$self->{rbuf};
1157 1285
1158 my $json = $self->{json} ||= JSON->new->utf8;
1159
1160 sub { 1286 sub {
1161 my $ref = $json->incr_parse ($self->{rbuf}); 1287 my $ref = eval { $json->incr_parse ($self->{rbuf}) };
1162 1288
1163 if ($ref) { 1289 if ($ref) {
1164 $self->{rbuf} = $json->incr_text; 1290 $self->{rbuf} = $json->incr_text;
1165 $json->incr_text = ""; 1291 $json->incr_text = "";
1166 $cb->($self, $ref); 1292 $cb->($self, $ref);
1167 1293
1168 1 1294 1
1295 } elsif ($@) {
1296 # error case
1297 $json->incr_skip;
1298
1299 $self->{rbuf} = $json->incr_text;
1300 $json->incr_text = "";
1301
1302 $self->_error (&Errno::EBADMSG);
1303
1304 ()
1169 } else { 1305 } else {
1170 $self->{rbuf} = ""; 1306 $self->{rbuf} = "";
1307
1171 () 1308 ()
1172 } 1309 }
1173 } 1310 }
1174}; 1311};
1175 1312
1252Note that AnyEvent::Handle will automatically C<start_read> for you when 1389Note that AnyEvent::Handle will automatically C<start_read> for you when
1253you change the C<on_read> callback or push/unshift a read callback, and it 1390you change the C<on_read> callback or push/unshift a read callback, and it
1254will automatically C<stop_read> for you when neither C<on_read> is set nor 1391will automatically C<stop_read> for you when neither C<on_read> is set nor
1255there are any read requests in the queue. 1392there are any read requests in the queue.
1256 1393
1394These methods will have no effect when in TLS mode (as TLS doesn't support
1395half-duplex connections).
1396
1257=cut 1397=cut
1258 1398
1259sub stop_read { 1399sub stop_read {
1260 my ($self) = @_; 1400 my ($self) = @_;
1261 1401
1262 delete $self->{_rw}; 1402 delete $self->{_rw} unless $self->{tls};
1263} 1403}
1264 1404
1265sub start_read { 1405sub start_read {
1266 my ($self) = @_; 1406 my ($self) = @_;
1267 1407
1268 unless ($self->{_rw} || $self->{_eof}) { 1408 unless ($self->{_rw} || $self->{_eof}) {
1269 Scalar::Util::weaken $self; 1409 Scalar::Util::weaken $self;
1270 1410
1271 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { 1411 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub {
1272 my $rbuf = $self->{filter_r} ? \my $buf : \$self->{rbuf}; 1412 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1273 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 1413 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf;
1274 1414
1275 if ($len > 0) { 1415 if ($len > 0) {
1276 $self->{_activity} = AnyEvent->now; 1416 $self->{_activity} = AnyEvent->now;
1277 1417
1278 $self->{filter_r} 1418 if ($self->{tls}) {
1279 ? $self->{filter_r}($self, $rbuf) 1419 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
1280 : $self->{_in_drain} || $self->_drain_rbuf; 1420
1421 &_dotls ($self);
1422 } else {
1423 $self->_drain_rbuf unless $self->{_in_drain};
1424 }
1281 1425
1282 } elsif (defined $len) { 1426 } elsif (defined $len) {
1283 delete $self->{_rw}; 1427 delete $self->{_rw};
1284 $self->{_eof} = 1; 1428 $self->{_eof} = 1;
1285 $self->_drain_rbuf unless $self->{_in_drain}; 1429 $self->_drain_rbuf unless $self->{_in_drain};
1289 } 1433 }
1290 }); 1434 });
1291 } 1435 }
1292} 1436}
1293 1437
1438our $ERROR_SYSCALL;
1439our $ERROR_WANT_READ;
1440
1441sub _tls_error {
1442 my ($self, $err) = @_;
1443
1444 return $self->_error ($!, 1)
1445 if $err == Net::SSLeay::ERROR_SYSCALL ();
1446
1447 my $err =Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ());
1448
1449 # reduce error string to look less scary
1450 $err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /;
1451
1452 if ($self->{_on_starttls}) {
1453 (delete $self->{_on_starttls})->($self, undef, $err);
1454 &_freetls;
1455 } else {
1456 &_freetls;
1457 $self->_error (&Errno::EPROTO, 1, $err);
1458 }
1459}
1460
1461# poll the write BIO and send the data if applicable
1462# also decode read data if possible
1463# this is basiclaly our TLS state machine
1464# more efficient implementations are possible with openssl,
1465# but not with the buggy and incomplete Net::SSLeay.
1294sub _dotls { 1466sub _dotls {
1295 my ($self) = @_; 1467 my ($self) = @_;
1296 1468
1297 my $buf; 1469 my $tmp;
1298 1470
1299 if (length $self->{_tls_wbuf}) { 1471 if (length $self->{_tls_wbuf}) {
1300 while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { 1472 while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {
1301 substr $self->{_tls_wbuf}, 0, $len, ""; 1473 substr $self->{_tls_wbuf}, 0, $tmp, "";
1302 } 1474 }
1303 }
1304 1475
1476 $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
1477 return $self->_tls_error ($tmp)
1478 if $tmp != $ERROR_WANT_READ
1479 && ($tmp != $ERROR_SYSCALL || $!);
1480 }
1481
1482 while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
1483 unless (length $tmp) {
1484 $self->{_on_starttls}
1485 and (delete $self->{_on_starttls})->($self, undef, "EOF during handshake"); # ???
1486 &_freetls;
1487
1488 if ($self->{on_stoptls}) {
1489 $self->{on_stoptls}($self);
1490 return;
1491 } else {
1492 # let's treat SSL-eof as we treat normal EOF
1493 delete $self->{_rw};
1494 $self->{_eof} = 1;
1495 }
1496 }
1497
1498 $self->{_tls_rbuf} .= $tmp;
1499 $self->_drain_rbuf unless $self->{_in_drain};
1500 $self->{tls} or return; # tls session might have gone away in callback
1501 }
1502
1503 $tmp = Net::SSLeay::get_error ($self->{tls}, -1);
1504 return $self->_tls_error ($tmp)
1505 if $tmp != $ERROR_WANT_READ
1506 && ($tmp != $ERROR_SYSCALL || $!);
1507
1305 if (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) { 1508 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1306 $self->{wbuf} .= $buf; 1509 $self->{wbuf} .= $tmp;
1307 $self->_drain_wbuf; 1510 $self->_drain_wbuf;
1308 } 1511 }
1309 1512
1310 while (defined ($buf = Net::SSLeay::read ($self->{tls}))) { 1513 $self->{_on_starttls}
1311 if (length $buf) { 1514 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
1312 $self->{rbuf} .= $buf; 1515 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
1313 $self->_drain_rbuf unless $self->{_in_drain};
1314 } else {
1315 # let's treat SSL-eof as we treat normal EOF
1316 $self->{_eof} = 1;
1317 $self->_shutdown;
1318 return;
1319 }
1320 }
1321
1322 my $err = Net::SSLeay::get_error ($self->{tls}, -1);
1323
1324 if ($err!= Net::SSLeay::ERROR_WANT_READ ()) {
1325 if ($err == Net::SSLeay::ERROR_SYSCALL ()) {
1326 return $self->_error ($!, 1);
1327 } elsif ($err == Net::SSLeay::ERROR_SSL ()) {
1328 return $self->_error (&Errno::EIO, 1);
1329 }
1330
1331 # all others are fine for our purposes
1332 }
1333} 1516}
1334 1517
1335=item $handle->starttls ($tls[, $tls_ctx]) 1518=item $handle->starttls ($tls[, $tls_ctx])
1336 1519
1337Instead of starting TLS negotiation immediately when the AnyEvent::Handle 1520Instead of starting TLS negotiation immediately when the AnyEvent::Handle
1339C<starttls>. 1522C<starttls>.
1340 1523
1341The first argument is the same as the C<tls> constructor argument (either 1524The first argument is the same as the C<tls> constructor argument (either
1342C<"connect">, C<"accept"> or an existing Net::SSLeay object). 1525C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1343 1526
1344The second argument is the optional C<Net::SSLeay::CTX> object that is 1527The second argument is the optional C<AnyEvent::TLS> object that is used
1345used when AnyEvent::Handle has to create its own TLS connection object. 1528when AnyEvent::Handle has to create its own TLS connection object, or
1529a hash reference with C<< key => value >> pairs that will be used to
1530construct a new context.
1346 1531
1347The TLS connection object will end up in C<< $handle->{tls} >> after this 1532The TLS connection object will end up in C<< $handle->{tls} >>, the TLS
1348call and can be used or changed to your liking. Note that the handshake 1533context in C<< $handle->{tls_ctx} >> after this call and can be used or
1349might have already started when this function returns. 1534changed to your liking. Note that the handshake might have already started
1535when this function returns.
1350 1536
1537If it an error to start a TLS handshake more than once per
1538AnyEvent::Handle object (this is due to bugs in OpenSSL).
1539
1351=cut 1540=cut
1541
1542our %TLS_CACHE; #TODO not yet documented, should we?
1352 1543
1353sub starttls { 1544sub starttls {
1354 my ($self, $ssl, $ctx) = @_; 1545 my ($self, $ssl, $ctx) = @_;
1355 1546
1356 $self->stoptls; 1547 require Net::SSLeay;
1357 1548
1358 if ($ssl eq "accept") { 1549 Carp::croak "it is an error to call starttls more than once on an AnyEvent::Handle object"
1359 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1550 if $self->{tls};
1360 Net::SSLeay::set_accept_state ($ssl); 1551
1361 } elsif ($ssl eq "connect") { 1552 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
1362 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1553 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
1363 Net::SSLeay::set_connect_state ($ssl); 1554
1555 $ctx ||= $self->{tls_ctx};
1556
1557 if ("HASH" eq ref $ctx) {
1558 require AnyEvent::TLS;
1559
1560 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context
1561
1562 if ($ctx->{cache}) {
1563 my $key = $ctx+0;
1564 $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx;
1565 } else {
1566 $ctx = new AnyEvent::TLS %$ctx;
1567 }
1568 }
1364 } 1569
1365 1570 $self->{tls_ctx} = $ctx || TLS_CTX ();
1366 $self->{tls} = $ssl; 1571 $self->{tls} = $ssl = $self->{tls_ctx}->_get_session ($ssl, $self, $self->{peername});
1367 1572
1368 # basically, this is deep magic (because SSL_read should have the same issues) 1573 # basically, this is deep magic (because SSL_read should have the same issues)
1369 # but the openssl maintainers basically said: "trust us, it just works". 1574 # but the openssl maintainers basically said: "trust us, it just works".
1370 # (unfortunately, we have to hardcode constants because the abysmally misdesigned 1575 # (unfortunately, we have to hardcode constants because the abysmally misdesigned
1371 # and mismaintained ssleay-module doesn't even offer them). 1576 # and mismaintained ssleay-module doesn't even offer them).
1372 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html 1577 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html
1373 # 1578 #
1374 # in short: this is a mess. 1579 # in short: this is a mess.
1375 # 1580 #
1376 # note that we do not try to kepe the length constant between writes as we are required to do. 1581 # note that we do not try to keep the length constant between writes as we are required to do.
1377 # we assume that most (but not all) of this insanity only applies to non-blocking cases, 1582 # we assume that most (but not all) of this insanity only applies to non-blocking cases,
1378 # and we drive openssl fully in blocking mode here. 1583 # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to
1584 # have identity issues in that area.
1379 Net::SSLeay::CTX_set_mode ($self->{tls}, 1585# Net::SSLeay::CTX_set_mode ($ssl,
1380 (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) 1586# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
1381 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); 1587# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
1588 Net::SSLeay::CTX_set_mode ($ssl, 1|2);
1382 1589
1383 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1590 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1384 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1591 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1385 1592
1386 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio}); 1593 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio});
1387 1594
1388 $self->{filter_w} = sub { 1595 $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
1389 $_[0]{_tls_wbuf} .= ${$_[1]}; 1596 if $self->{on_starttls};
1390 &_dotls; 1597
1391 }; 1598 &_dotls; # need to trigger the initial handshake
1392 $self->{filter_r} = sub { 1599 $self->start_read; # make sure we actually do read
1393 Net::SSLeay::BIO_write ($_[0]{_rbio}, ${$_[1]});
1394 &_dotls;
1395 };
1396} 1600}
1397 1601
1398=item $handle->stoptls 1602=item $handle->stoptls
1399 1603
1400Destroys the SSL connection, if any. Partial read or write data will be 1604Shuts down the SSL connection - this makes a proper EOF handshake by
1401lost. 1605sending a close notify to the other side, but since OpenSSL doesn't
1606support non-blocking shut downs, it is not possible to re-use the stream
1607afterwards.
1402 1608
1403=cut 1609=cut
1404 1610
1405sub stoptls { 1611sub stoptls {
1406 my ($self) = @_; 1612 my ($self) = @_;
1407 1613
1408 Net::SSLeay::free (delete $self->{tls}) if $self->{tls}; 1614 if ($self->{tls}) {
1615 Net::SSLeay::shutdown ($self->{tls});
1409 1616
1410 delete $self->{_rbio}; 1617 &_dotls;
1411 delete $self->{_wbio}; 1618
1412 delete $self->{_tls_wbuf}; 1619# # we don't give a shit. no, we do, but we can't. no...#d#
1413 delete $self->{filter_r}; 1620# # we, we... have to use openssl :/#d#
1414 delete $self->{filter_w}; 1621# &_freetls;#d#
1622 }
1623}
1624
1625sub _freetls {
1626 my ($self) = @_;
1627
1628 return unless $self->{tls};
1629
1630 $self->{tls_ctx}->_put_session (delete $self->{tls});
1631
1632 delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};
1415} 1633}
1416 1634
1417sub DESTROY { 1635sub DESTROY {
1418 my $self = shift; 1636 my ($self) = @_;
1419 1637
1420 $self->stoptls; 1638 &_freetls;
1421 1639
1422 my $linger = exists $self->{linger} ? $self->{linger} : 3600; 1640 my $linger = exists $self->{linger} ? $self->{linger} : 3600;
1423 1641
1424 if ($linger && length $self->{wbuf}) { 1642 if ($linger && length $self->{wbuf}) {
1425 my $fh = delete $self->{fh}; 1643 my $fh = delete $self->{fh};
1440 @linger = (); 1658 @linger = ();
1441 }); 1659 });
1442 } 1660 }
1443} 1661}
1444 1662
1663=item $handle->destroy
1664
1665Shuts down the handle object as much as possible - this call ensures that
1666no further callbacks will be invoked and as many resources as possible
1667will be freed. You must not call any methods on the object afterwards.
1668
1669Normally, you can just "forget" any references to an AnyEvent::Handle
1670object and it will simply shut down. This works in fatal error and EOF
1671callbacks, as well as code outside. It does I<NOT> work in a read or write
1672callback, so when you want to destroy the AnyEvent::Handle object from
1673within such an callback. You I<MUST> call C<< ->destroy >> explicitly in
1674that case.
1675
1676The handle might still linger in the background and write out remaining
1677data, as specified by the C<linger> option, however.
1678
1679=cut
1680
1681sub destroy {
1682 my ($self) = @_;
1683
1684 $self->DESTROY;
1685 %$self = ();
1686}
1687
1445=item AnyEvent::Handle::TLS_CTX 1688=item AnyEvent::Handle::TLS_CTX
1446 1689
1447This function creates and returns the Net::SSLeay::CTX object used by 1690This function creates and returns the AnyEvent::TLS object used by default
1448default for TLS mode. 1691for TLS mode.
1449 1692
1450The context is created like this: 1693The context is created by calling L<AnyEvent::TLS> without any arguments.
1451
1452 Net::SSLeay::load_error_strings;
1453 Net::SSLeay::SSLeay_add_ssl_algorithms;
1454 Net::SSLeay::randomize;
1455
1456 my $CTX = Net::SSLeay::CTX_new;
1457
1458 Net::SSLeay::CTX_set_options $CTX, Net::SSLeay::OP_ALL
1459 1694
1460=cut 1695=cut
1461 1696
1462our $TLS_CTX; 1697our $TLS_CTX;
1463 1698
1464sub TLS_CTX() { 1699sub TLS_CTX() {
1465 $TLS_CTX || do { 1700 $TLS_CTX ||= do {
1466 require Net::SSLeay; 1701 require AnyEvent::TLS;
1467 1702
1468 Net::SSLeay::load_error_strings (); 1703 new AnyEvent::TLS
1469 Net::SSLeay::SSLeay_add_ssl_algorithms ();
1470 Net::SSLeay::randomize ();
1471
1472 $TLS_CTX = Net::SSLeay::CTX_new ();
1473
1474 Net::SSLeay::CTX_set_options ($TLS_CTX, Net::SSLeay::OP_ALL ());
1475
1476 $TLS_CTX
1477 } 1704 }
1478} 1705}
1479 1706
1480=back 1707=back
1708
1709
1710=head1 NONFREQUENTLY ASKED QUESTIONS
1711
1712=over 4
1713
1714=item I C<undef> the AnyEvent::Handle reference inside my callback and
1715still get further invocations!
1716
1717That's because AnyEvent::Handle keeps a reference to itself when handling
1718read or write callbacks.
1719
1720It is only safe to "forget" the reference inside EOF or error callbacks,
1721from within all other callbacks, you need to explicitly call the C<<
1722->destroy >> method.
1723
1724=item I get different callback invocations in TLS mode/Why can't I pause
1725reading?
1726
1727Unlike, say, TCP, TLS connections do not consist of two independent
1728communication channels, one for each direction. Or put differently. The
1729read and write directions are not independent of each other: you cannot
1730write data unless you are also prepared to read, and vice versa.
1731
1732This can mean than, in TLS mode, you might get C<on_error> or C<on_eof>
1733callback invocations when you are not expecting any read data - the reason
1734is that AnyEvent::Handle always reads in TLS mode.
1735
1736During the connection, you have to make sure that you always have a
1737non-empty read-queue, or an C<on_read> watcher. At the end of the
1738connection (or when you no longer want to use it) you can call the
1739C<destroy> method.
1740
1741=item How do I read data until the other side closes the connection?
1742
1743If you just want to read your data into a perl scalar, the easiest way
1744to achieve this is by setting an C<on_read> callback that does nothing,
1745clearing the C<on_eof> callback and in the C<on_error> callback, the data
1746will be in C<$_[0]{rbuf}>:
1747
1748 $handle->on_read (sub { });
1749 $handle->on_eof (undef);
1750 $handle->on_error (sub {
1751 my $data = delete $_[0]{rbuf};
1752 undef $handle;
1753 });
1754
1755The reason to use C<on_error> is that TCP connections, due to latencies
1756and packets loss, might get closed quite violently with an error, when in
1757fact, all data has been received.
1758
1759It is usually better to use acknowledgements when transferring data,
1760to make sure the other side hasn't just died and you got the data
1761intact. This is also one reason why so many internet protocols have an
1762explicit QUIT command.
1763
1764=item I don't want to destroy the handle too early - how do I wait until
1765all data has been written?
1766
1767After writing your last bits of data, set the C<on_drain> callback
1768and destroy the handle in there - with the default setting of
1769C<low_water_mark> this will be called precisely when all data has been
1770written to the socket:
1771
1772 $handle->push_write (...);
1773 $handle->on_drain (sub {
1774 warn "all data submitted to the kernel\n";
1775 undef $handle;
1776 });
1777
1778If you just want to queue some data and then signal EOF to the other side,
1779consider using C<< ->push_shutdown >> instead.
1780
1781=item I want to contact a TLS/SSL server, I don't care about security.
1782
1783If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
1784simply connect to it and then create the AnyEvent::Handle with the C<tls>
1785parameter:
1786
1787 tcp_connect $host, $port, sub {
1788 my ($fh) = @_;
1789
1790 my $handle = new AnyEvent::Handle
1791 fh => $fh,
1792 tls => "connect",
1793 on_error => sub { ... };
1794
1795 $handle->push_write (...);
1796 };
1797
1798=item I want to contact a TLS/SSL server, I do care about security.
1799
1800Then you should additionally enable certificate verification, including
1801peername verification, if the protocol you use supports it (see
1802L<AnyEvent::TLS>, C<verify_peername>).
1803
1804E.g. for HTTPS:
1805
1806 tcp_connect $host, $port, sub {
1807 my ($fh) = @_;
1808
1809 my $handle = new AnyEvent::Handle
1810 fh => $fh,
1811 peername => $host,
1812 tls => "connect",
1813 tls_ctx => { verify => 1, verify_peername => "https" },
1814 ...
1815
1816Note that you must specify the hostname you connected to (or whatever
1817"peername" the protocol needs) as the C<peername> argument, otherwise no
1818peername verification will be done.
1819
1820The above will use the system-dependent default set of trusted CA
1821certificates. If you want to check against a specific CA, add the
1822C<ca_file> (or C<ca_cert>) arguments to C<tls_ctx>:
1823
1824 tls_ctx => {
1825 verify => 1,
1826 verify_peername => "https",
1827 ca_file => "my-ca-cert.pem",
1828 },
1829
1830=item I want to create a TLS/SSL server, how do I do that?
1831
1832Well, you first need to get a server certificate and key. You have
1833three options: a) ask a CA (buy one, use cacert.org etc.) b) create a
1834self-signed certificate (cheap. check the search engine of your choice,
1835there are many tutorials on the net) or c) make your own CA (tinyca2 is a
1836nice program for that purpose).
1837
1838Then create a file with your private key (in PEM format, see
1839L<AnyEvent::TLS>), followed by the certificate (also in PEM format). The
1840file should then look like this:
1841
1842 -----BEGIN RSA PRIVATE KEY-----
1843 ...header data
1844 ... lots of base64'y-stuff
1845 -----END RSA PRIVATE KEY-----
1846
1847 -----BEGIN CERTIFICATE-----
1848 ... lots of base64'y-stuff
1849 -----END CERTIFICATE-----
1850
1851The important bits are the "PRIVATE KEY" and "CERTIFICATE" parts. Then
1852specify this file as C<cert_file>:
1853
1854 tcp_server undef, $port, sub {
1855 my ($fh) = @_;
1856
1857 my $handle = new AnyEvent::Handle
1858 fh => $fh,
1859 tls => "accept",
1860 tls_ctx => { cert_file => "my-server-keycert.pem" },
1861 ...
1862
1863When you have intermediate CA certificates that your clients might not
1864know about, just append them to the C<cert_file>.
1865
1866=back
1867
1481 1868
1482=head1 SUBCLASSING AnyEvent::Handle 1869=head1 SUBCLASSING AnyEvent::Handle
1483 1870
1484In many cases, you might want to subclass AnyEvent::Handle. 1871In many cases, you might want to subclass AnyEvent::Handle.
1485 1872

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines