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.79 by root, Sun Jul 27 08:37:56 2008 UTC vs.
Revision 1.143 by root, Mon Jul 6 21:02:34 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.22; 19our $VERSION = 4.452;
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");
49 49
50This module is a helper module to make it easier to do event-based I/O on 50This module is a helper module to make it easier to do event-based I/O on
51filehandles. For utility functions for doing non-blocking connects and accepts 51filehandles. For utility functions for doing non-blocking connects and accepts
52on sockets see L<AnyEvent::Util>. 52on sockets see L<AnyEvent::Util>.
53 53
54The L<AnyEvent::Intro> tutorial contains some well-documented
55AnyEvent::Handle examples.
56
54In the following, when the documentation refers to of "bytes" then this 57In the following, when the documentation refers to of "bytes" then this
55means characters. As sysread and syswrite are used for all I/O, their 58means characters. As sysread and syswrite are used for all I/O, their
56treatment of characters applies to this module as well. 59treatment of characters applies to this module as well.
57 60
58All callbacks will be invoked with the handle object as their first 61All callbacks will be invoked with the handle object as their first
60 63
61=head1 METHODS 64=head1 METHODS
62 65
63=over 4 66=over 4
64 67
65=item B<new (%args)> 68=item $handle = B<new> AnyEvent::TLS fh => $filehandle, key => value...
66 69
67The constructor supports these arguments (all as key => value pairs). 70The constructor supports these arguments (all as C<< key => value >> pairs).
68 71
69=over 4 72=over 4
70 73
71=item fh => $filehandle [MANDATORY] 74=item fh => $filehandle [MANDATORY]
72 75
73The filehandle this L<AnyEvent::Handle> object will operate on. 76The filehandle this L<AnyEvent::Handle> object will operate on.
74 77
75NOTE: The filehandle will be set to non-blocking (using 78NOTE: The filehandle will be set to non-blocking mode (using
76AnyEvent::Util::fh_nonblocking). 79C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in
80that mode.
77 81
78=item on_eof => $cb->($handle) 82=item on_eof => $cb->($handle)
79 83
80Set 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,
81i.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
82connection cleanly. 86connection cleanly.
83 87
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
90callback and continue writing data, as only the read part has been shut
91down.
92
84While not mandatory, it is highly recommended to set an eof callback, 93While not mandatory, it is I<highly> recommended to set an EOF callback,
85otherwise 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
86waiting for data. 95waiting for data.
87 96
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>.
99
88=item on_error => $cb->($handle, $fatal) 100=item on_error => $cb->($handle, $fatal, $message)
89 101
90This is the error callback, which is called when, well, some error 102This is the error callback, which is called when, well, some error
91occured, such as not being able to resolve the hostname, failure to 103occured, such as not being able to resolve the hostname, failure to
92connect or a read error. 104connect or a read error.
93 105
94Some 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
95fatal errors the handle object will be shut down and will not be 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
109errors are an EOF condition with active (but unsatisifable) read watchers
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<"$!">).
116
96usable. Non-fatal errors can be retried by simply returning, but it is 117Non-fatal errors can be retried by simply returning, but it is recommended
97recommended to simply ignore this parameter and instead abondon the handle 118to simply ignore this parameter and instead abondon the handle object
98object when this callback is invoked. 119when this callback is invoked. Examples of non-fatal errors are timeouts
120C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
99 121
100On callback entrance, the value of C<$!> contains the operating system 122On callback entrance, the value of C<$!> contains the operating system
101error (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT> or C<EBADMSG>). 123error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
124C<EPROTO>).
102 125
103While 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
104you will not be notified of errors otherwise. The default simply calls 127you will not be notified of errors otherwise. The default simply calls
105C<croak>. 128C<croak>.
106 129
110and 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
111callback 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
112read buffer). 135read buffer).
113 136
114To 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 >>
115method 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.
116 141
117When 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
118feed 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
119calling 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
120error will be raised (with C<$!> set to C<EPIPE>). 145error will be raised (with C<$!> set to C<EPIPE>).
135=item timeout => $fractional_seconds 160=item timeout => $fractional_seconds
136 161
137If non-zero, then this enables an "inactivity" timeout: whenever this many 162If non-zero, then this enables an "inactivity" timeout: whenever this many
138seconds pass without a successful read or write on the underlying file 163seconds pass without a successful read or write on the underlying file
139handle, 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
140missing, an C<ETIMEDOUT> error will be raised). 165missing, a non-fatal C<ETIMEDOUT> error will be raised).
141 166
142Note 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
143any 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
144idle then you should disable the timout temporarily or ignore the timeout 169idle then you should disable the timout temporarily or ignore the timeout
145in the C<on_timeout> callback. 170in the C<on_timeout> callback, in which case AnyEvent::Handle will simply
171restart the timeout.
146 172
147Zero (the default) disables this timeout. 173Zero (the default) disables this timeout.
148 174
149=item on_timeout => $cb->($handle) 175=item on_timeout => $cb->($handle)
150 176
154 180
155=item rbuf_max => <bytes> 181=item rbuf_max => <bytes>
156 182
157If 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>)
158when 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
159avoid denial-of-service attacks. 185avoid some forms of denial-of-service attacks.
160 186
161For example, a server accepting connections from untrusted sources should 187For example, a server accepting connections from untrusted sources should
162be 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
163(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
164amount 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
165isn't finished). 191isn't finished).
166 192
167=item autocork => <boolean> 193=item autocork => <boolean>
168 194
169When disabled (the default), then C<push_write> will try to immediately 195When disabled (the default), then C<push_write> will try to immediately
170write 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
171a 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
172inefficient if you write multiple small chunks (this disadvantage is 198be inefficient if you write multiple small chunks (on the wire, this
173usually 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).
174 201
175When 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
176iteration. This is efficient when you do many small writes per iteration, 203iteration. This is efficient when you do many small writes per iteration,
177but 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.
178 206
179=item no_delay => <boolean> 207=item no_delay => <boolean>
180 208
181When doing small writes on sockets, your operating system kernel might 209When doing small writes on sockets, your operating system kernel might
182wait 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
183the Nagle algorithm, and usually it is beneficial. 211the Nagle algorithm, and usually it is beneficial.
184 212
185In 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
186accomplishd by setting this option to true. 214accomplishd by setting this option to a true value.
187 215
188The default is your opertaing system's default behaviour, this option 216The default is your opertaing system's default behaviour (most likely
189explicitly enables or disables it, if possible. 217enabled), this option explicitly enables or disables it, if possible.
190 218
191=item read_size => <bytes> 219=item read_size => <bytes>
192 220
193The 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
194during each (loop iteration). Default: C<8192>. 222try to read during each loop iteration, which affects memory
223requirements). Default: C<8192>.
195 224
196=item low_water_mark => <bytes> 225=item low_water_mark => <bytes>
197 226
198Sets 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
199buffer: 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
200considered empty. 229considered empty.
201 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
202=item linger => <seconds> 236=item linger => <seconds>
203 237
204If non-zero (default: C<3600>), then the destructor of the 238If non-zero (default: C<3600>), then the destructor of the
205AnyEvent::Handle object will check wether there is still outstanding write 239AnyEvent::Handle object will check whether there is still outstanding
206data 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
207will be reported (this mostly matches how the operating system treats 241socket. No errors will be reported (this mostly matches how the operating
208outstanding data at socket close time). 242system treats outstanding data at socket close time).
209 243
210This 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
211encoded. 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>).
212 255
213=item tls => "accept" | "connect" | Net::SSLeay::SSL object 256=item tls => "accept" | "connect" | Net::SSLeay::SSL object
214 257
215When this parameter is given, it enables TLS (SSL) mode, that means it 258When this parameter is given, it enables TLS (SSL) mode, that means
216will start making tls handshake and will transparently encrypt/decrypt 259AnyEvent will start a TLS handshake as soon as the conenction has been
217data. 260established and will transparently encrypt/decrypt data afterwards.
261
262All TLS protocol errors will be signalled as C<EPROTO>, with an
263appropriate error message.
218 264
219TLS mode requires Net::SSLeay to be installed (it will be loaded 265TLS mode requires Net::SSLeay to be installed (it will be loaded
220automatically when you try to create a TLS handle). 266automatically when you try to create a TLS handle): this module doesn't
267have a dependency on that module, so if your module requires it, you have
268to add the dependency yourself.
221 269
222For the TLS server side, use C<accept>, and for the TLS client side of a 270Unlike TCP, TLS has a server and client side: for the TLS server side, use
223connection, use C<connect> mode. 271C<accept>, and for the TLS client side of a connection, use C<connect>
272mode.
224 273
225You can also provide your own TLS connection object, but you have 274You can also provide your own TLS connection object, but you have
226to make sure that you call either C<Net::SSLeay::set_connect_state> 275to make sure that you call either C<Net::SSLeay::set_connect_state>
227or C<Net::SSLeay::set_accept_state> on it before you pass it to 276or C<Net::SSLeay::set_accept_state> on it before you pass it to
228AnyEvent::Handle. 277AnyEvent::Handle. Also, this module will take ownership of this connection
278object.
229 279
280At some future point, AnyEvent::Handle might switch to another TLS
281implementation, then the option to use your own session object will go
282away.
283
284B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
285passing in the wrong integer will lead to certain crash. This most often
286happens when one uses a stylish C<< tls => 1 >> and is surprised about the
287segmentation fault.
288
230See the C<starttls> method if you need to start TLS negotiation later. 289See the C<< ->starttls >> method for when need to start TLS negotiation later.
231 290
232=item tls_ctx => $ssl_ctx 291=item tls_ctx => $anyevent_tls
233 292
234Use the given Net::SSLeay::CTX object to create the new TLS connection 293Use the given C<AnyEvent::TLS> object to create the new TLS connection
235(unless a connection object was specified directly). If this parameter is 294(unless a connection object was specified directly). If this parameter is
236missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. 295missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>.
237 296
297Instead of an object, you can also specify a hash reference with C<< key
298=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a
299new TLS context object.
300
301=item on_starttls => $cb->($handle, $success[, $error_message])
302
303This callback will be invoked when the TLS/SSL handshake has finished. If
304C<$success> is true, then the TLS handshake succeeded, otherwise it failed
305(C<on_stoptls> will not be called in this case).
306
307The session in C<< $handle->{tls} >> can still be examined in this
308callback, even when the handshake was not successful.
309
310TLS handshake failures will not cause C<on_error> to be invoked when this
311callback is in effect, instead, the error message will be passed to C<on_starttls>.
312
313Without this callback, handshake failures lead to C<on_error> being
314called, as normal.
315
316Note that you cannot call C<starttls> right again in this callback. If you
317need to do that, start an zero-second timer instead whose callback can
318then call C<< ->starttls >> again.
319
320=item on_stoptls => $cb->($handle)
321
322When a SSLv3/TLS shutdown/close notify/EOF is detected and this callback is
323set, then it will be invoked after freeing the TLS session. If it is not,
324then a TLS shutdown condition will be treated like a normal EOF condition
325on the handle.
326
327The session in C<< $handle->{tls} >> can still be examined in this
328callback.
329
330This callback will only be called on TLS shutdowns, not when the
331underlying handle signals EOF.
332
238=item json => JSON or JSON::XS object 333=item json => JSON or JSON::XS object
239 334
240This is the json coder object used by the C<json> read and write types. 335This is the json coder object used by the C<json> read and write types.
241 336
242If you don't supply it, then AnyEvent::Handle will create and use a 337If you don't supply it, then AnyEvent::Handle will create and use a
243suitable one, which will write and expect UTF-8 encoded JSON texts. 338suitable one (on demand), which will write and expect UTF-8 encoded JSON
339texts.
244 340
245Note that you are responsible to depend on the JSON module if you want to 341Note that you are responsible to depend on the JSON module if you want to
246use this functionality, as AnyEvent does not have a dependency itself. 342use this functionality, as AnyEvent does not have a dependency itself.
247 343
248=item filter_r => $cb
249
250=item filter_w => $cb
251
252These exist, but are undocumented at this time.
253
254=back 344=back
255 345
256=cut 346=cut
257 347
258sub new { 348sub new {
259 my $class = shift; 349 my $class = shift;
260
261 my $self = bless { @_ }, $class; 350 my $self = bless { @_ }, $class;
262 351
263 $self->{fh} or Carp::croak "mandatory argument fh is missing"; 352 $self->{fh} or Carp::croak "mandatory argument fh is missing";
264 353
265 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 354 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
266
267 if ($self->{tls}) {
268 require Net::SSLeay;
269 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx});
270 }
271 355
272 $self->{_activity} = AnyEvent->now; 356 $self->{_activity} = AnyEvent->now;
273 $self->_timeout; 357 $self->_timeout;
274 358
275 $self->on_drain (delete $self->{on_drain}) if exists $self->{on_drain};
276 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay}; 359 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay};
360
361 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
362 if $self->{tls};
363
364 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain};
277 365
278 $self->start_read 366 $self->start_read
279 if $self->{on_read}; 367 if $self->{on_read};
280 368
281 $self 369 $self->{fh} && $self
282} 370}
283 371
284sub _shutdown { 372sub _shutdown {
285 my ($self) = @_; 373 my ($self) = @_;
286 374
287 delete $self->{_tw}; 375 delete @$self{qw(_tw _rw _ww fh wbuf on_read _queue)};
288 delete $self->{_rw}; 376 $self->{_eof} = 1; # tell starttls et. al to stop trying
289 delete $self->{_ww};
290 delete $self->{fh};
291 377
292 $self->stoptls; 378 &_freetls;
293} 379}
294 380
295sub _error { 381sub _error {
296 my ($self, $errno, $fatal) = @_; 382 my ($self, $errno, $fatal, $message) = @_;
297 383
298 $self->_shutdown 384 $self->_shutdown
299 if $fatal; 385 if $fatal;
300 386
301 $! = $errno; 387 $! = $errno;
388 $message ||= "$!";
302 389
303 if ($self->{on_error}) { 390 if ($self->{on_error}) {
304 $self->{on_error}($self, $fatal); 391 $self->{on_error}($self, $fatal, $message);
305 } else { 392 } elsif ($self->{fh}) {
306 Carp::croak "AnyEvent::Handle uncaught error: $!"; 393 Carp::croak "AnyEvent::Handle uncaught error: $message";
307 } 394 }
308} 395}
309 396
310=item $fh = $handle->fh 397=item $fh = $handle->fh
311 398
312This method returns the file handle of the L<AnyEvent::Handle> object. 399This method returns the file handle used to create the L<AnyEvent::Handle> object.
313 400
314=cut 401=cut
315 402
316sub fh { $_[0]{fh} } 403sub fh { $_[0]{fh} }
317 404
335 $_[0]{on_eof} = $_[1]; 422 $_[0]{on_eof} = $_[1];
336} 423}
337 424
338=item $handle->on_timeout ($cb) 425=item $handle->on_timeout ($cb)
339 426
340Replace the current C<on_timeout> callback, or disables the callback 427Replace the current C<on_timeout> callback, or disables the callback (but
341(but not the timeout) if C<$cb> = C<undef>. See C<timeout> constructor 428not the timeout) if C<$cb> = C<undef>. See the C<timeout> constructor
342argument. 429argument and method.
343 430
344=cut 431=cut
345 432
346sub on_timeout { 433sub on_timeout {
347 $_[0]{on_timeout} = $_[1]; 434 $_[0]{on_timeout} = $_[1];
348} 435}
349 436
350=item $handle->autocork ($boolean) 437=item $handle->autocork ($boolean)
351 438
352Enables or disables the current autocork behaviour (see C<autocork> 439Enables or disables the current autocork behaviour (see C<autocork>
353constructor argument). 440constructor argument). Changes will only take effect on the next write.
354 441
355=cut 442=cut
443
444sub autocork {
445 $_[0]{autocork} = $_[1];
446}
356 447
357=item $handle->no_delay ($boolean) 448=item $handle->no_delay ($boolean)
358 449
359Enables or disables the C<no_delay> setting (see constructor argument of 450Enables or disables the C<no_delay> setting (see constructor argument of
360the same name for details). 451the same name for details).
366 457
367 eval { 458 eval {
368 local $SIG{__DIE__}; 459 local $SIG{__DIE__};
369 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1]; 460 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1];
370 }; 461 };
462}
463
464=item $handle->on_starttls ($cb)
465
466Replace the current C<on_starttls> callback (see the C<on_starttls> constructor argument).
467
468=cut
469
470sub on_starttls {
471 $_[0]{on_starttls} = $_[1];
472}
473
474=item $handle->on_stoptls ($cb)
475
476Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument).
477
478=cut
479
480sub on_starttls {
481 $_[0]{on_stoptls} = $_[1];
371} 482}
372 483
373############################################################################# 484#############################################################################
374 485
375=item $handle->timeout ($seconds) 486=item $handle->timeout ($seconds)
453 my ($self, $cb) = @_; 564 my ($self, $cb) = @_;
454 565
455 $self->{on_drain} = $cb; 566 $self->{on_drain} = $cb;
456 567
457 $cb->($self) 568 $cb->($self)
458 if $cb && $self->{low_water_mark} >= length $self->{wbuf}; 569 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
459} 570}
460 571
461=item $handle->push_write ($data) 572=item $handle->push_write ($data)
462 573
463Queues the given scalar to be written. You can push as much data as you 574Queues the given scalar to be written. You can push as much data as you
480 substr $self->{wbuf}, 0, $len, ""; 591 substr $self->{wbuf}, 0, $len, "";
481 592
482 $self->{_activity} = AnyEvent->now; 593 $self->{_activity} = AnyEvent->now;
483 594
484 $self->{on_drain}($self) 595 $self->{on_drain}($self)
485 if $self->{low_water_mark} >= length $self->{wbuf} 596 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
486 && $self->{on_drain}; 597 && $self->{on_drain};
487 598
488 delete $self->{_ww} unless length $self->{wbuf}; 599 delete $self->{_ww} unless length $self->{wbuf};
489 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 600 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
490 $self->_error ($!, 1); 601 $self->_error ($!, 1);
514 625
515 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") 626 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write")
516 ->($self, @_); 627 ->($self, @_);
517 } 628 }
518 629
519 if ($self->{filter_w}) { 630 if ($self->{tls}) {
520 $self->{filter_w}($self, \$_[0]); 631 $self->{_tls_wbuf} .= $_[0];
632
633 &_dotls ($self);
521 } else { 634 } else {
522 $self->{wbuf} .= $_[0]; 635 $self->{wbuf} .= $_[0];
523 $self->_drain_wbuf; 636 $self->_drain_wbuf;
524 } 637 }
525} 638}
542=cut 655=cut
543 656
544register_write_type netstring => sub { 657register_write_type netstring => sub {
545 my ($self, $string) = @_; 658 my ($self, $string) = @_;
546 659
547 sprintf "%d:%s,", (length $string), $string 660 (length $string) . ":$string,"
548}; 661};
549 662
550=item packstring => $format, $data 663=item packstring => $format, $data
551 664
552An octet string prefixed with an encoded length. The encoding C<$format> 665An octet string prefixed with an encoded length. The encoding C<$format>
617 730
618 pack "w/a*", Storable::nfreeze ($ref) 731 pack "w/a*", Storable::nfreeze ($ref)
619}; 732};
620 733
621=back 734=back
735
736=item $handle->push_shutdown
737
738Sometimes you know you want to close the socket after writing your data
739before it was actually written. One way to do that is to replace your
740C<on_drain> handler by a callback that shuts down the socket (and set
741C<low_water_mark> to C<0>). This method is a shorthand for just that, and
742replaces the C<on_drain> callback with:
743
744 sub { shutdown $_[0]{fh}, 1 } # for push_shutdown
745
746This simply shuts down the write side and signals an EOF condition to the
747the peer.
748
749You can rely on the normal read queue and C<on_eof> handling
750afterwards. This is the cleanest way to close a connection.
751
752=cut
753
754sub push_shutdown {
755 my ($self) = @_;
756
757 delete $self->{low_water_mark};
758 $self->on_drain (sub { shutdown $_[0]{fh}, 1 });
759}
622 760
623=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args) 761=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args)
624 762
625This function (not method) lets you add your own types to C<push_write>. 763This function (not method) lets you add your own types to C<push_write>.
626Whenever the given C<type> is used, C<push_write> will invoke the code 764Whenever the given C<type> is used, C<push_write> will invoke the code
726 864
727 if ( 865 if (
728 defined $self->{rbuf_max} 866 defined $self->{rbuf_max}
729 && $self->{rbuf_max} < length $self->{rbuf} 867 && $self->{rbuf_max} < length $self->{rbuf}
730 ) { 868 ) {
731 return $self->_error (&Errno::ENOSPC, 1); 869 $self->_error (&Errno::ENOSPC, 1), return;
732 } 870 }
733 871
734 while () { 872 while () {
873 # we need to use a separate tls read buffer, as we must not receive data while
874 # we are draining the buffer, and this can only happen with TLS.
875 $self->{rbuf} .= delete $self->{_tls_rbuf} if exists $self->{_tls_rbuf};
876
735 my $len = length $self->{rbuf}; 877 my $len = length $self->{rbuf};
736 878
737 if (my $cb = shift @{ $self->{_queue} }) { 879 if (my $cb = shift @{ $self->{_queue} }) {
738 unless ($cb->($self)) { 880 unless ($cb->($self)) {
739 if ($self->{_eof}) { 881 if ($self->{_eof}) {
740 # no progress can be made (not enough data and no data forthcoming) 882 # no progress can be made (not enough data and no data forthcoming)
741 $self->_error (&Errno::EPIPE, 1), last; 883 $self->_error (&Errno::EPIPE, 1), return;
742 } 884 }
743 885
744 unshift @{ $self->{_queue} }, $cb; 886 unshift @{ $self->{_queue} }, $cb;
745 last; 887 last;
746 } 888 }
754 && !@{ $self->{_queue} } # and the queue is still empty 896 && !@{ $self->{_queue} } # and the queue is still empty
755 && $self->{on_read} # but we still have on_read 897 && $self->{on_read} # but we still have on_read
756 ) { 898 ) {
757 # no further data will arrive 899 # no further data will arrive
758 # so no progress can be made 900 # so no progress can be made
759 $self->_error (&Errno::EPIPE, 1), last 901 $self->_error (&Errno::EPIPE, 1), return
760 if $self->{_eof}; 902 if $self->{_eof};
761 903
762 last; # more data might arrive 904 last; # more data might arrive
763 } 905 }
764 } else { 906 } else {
765 # read side becomes idle 907 # read side becomes idle
766 delete $self->{_rw}; 908 delete $self->{_rw} unless $self->{tls};
767 last; 909 last;
768 } 910 }
769 } 911 }
770 912
913 if ($self->{_eof}) {
914 if ($self->{on_eof}) {
771 $self->{on_eof}($self) 915 $self->{on_eof}($self)
772 if $self->{_eof} && $self->{on_eof}; 916 } else {
917 $self->_error (0, 1, "Unexpected end-of-file");
918 }
919 }
773 920
774 # may need to restart read watcher 921 # may need to restart read watcher
775 unless ($self->{_rw}) { 922 unless ($self->{_rw}) {
776 $self->start_read 923 $self->start_read
777 if $self->{on_read} || @{ $self->{_queue} }; 924 if $self->{on_read} || @{ $self->{_queue} };
795 942
796=item $handle->rbuf 943=item $handle->rbuf
797 944
798Returns the read buffer (as a modifiable lvalue). 945Returns the read buffer (as a modifiable lvalue).
799 946
800You can access the read buffer directly as the C<< ->{rbuf} >> member, if 947You can access the read buffer directly as the C<< ->{rbuf} >>
801you want. 948member, if you want. However, the only operation allowed on the
949read buffer (apart from looking at it) is removing data from its
950beginning. Otherwise modifying or appending to it is not allowed and will
951lead to hard-to-track-down bugs.
802 952
803NOTE: The read buffer should only be used or modified if the C<on_read>, 953NOTE: The read buffer should only be used or modified if the C<on_read>,
804C<push_read> or C<unshift_read> methods are used. The other read methods 954C<push_read> or C<unshift_read> methods are used. The other read methods
805automatically manage the read buffer. 955automatically manage the read buffer.
806 956
1061An octet string prefixed with an encoded length. The encoding C<$format> 1211An octet string prefixed with an encoded length. The encoding C<$format>
1062uses the same format as a Perl C<pack> format, but must specify a single 1212uses the same format as a Perl C<pack> format, but must specify a single
1063integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an 1213integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an
1064optional C<!>, C<< < >> or C<< > >> modifier). 1214optional C<!>, C<< < >> or C<< > >> modifier).
1065 1215
1066DNS over TCP uses a prefix of C<n>, EPP uses a prefix of C<N>. 1216For example, DNS over TCP uses a prefix of C<n> (2 octet network order),
1217EPP uses a prefix of C<N> (4 octtes).
1067 1218
1068Example: read a block of data prefixed by its length in BER-encoded 1219Example: read a block of data prefixed by its length in BER-encoded
1069format (very efficient). 1220format (very efficient).
1070 1221
1071 $handle->push_read (packstring => "w", sub { 1222 $handle->push_read (packstring => "w", sub {
1101 } 1252 }
1102}; 1253};
1103 1254
1104=item json => $cb->($handle, $hash_or_arrayref) 1255=item json => $cb->($handle, $hash_or_arrayref)
1105 1256
1106Reads a JSON object or array, decodes it and passes it to the callback. 1257Reads a JSON object or array, decodes it and passes it to the
1258callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1107 1259
1108If a C<json> object was passed to the constructor, then that will be used 1260If a C<json> object was passed to the constructor, then that will be used
1109for the final decode, otherwise it will create a JSON coder expecting UTF-8. 1261for the final decode, otherwise it will create a JSON coder expecting UTF-8.
1110 1262
1111This read type uses the incremental parser available with JSON version 1263This read type uses the incremental parser available with JSON version
1120=cut 1272=cut
1121 1273
1122register_read_type json => sub { 1274register_read_type json => sub {
1123 my ($self, $cb) = @_; 1275 my ($self, $cb) = @_;
1124 1276
1125 require JSON; 1277 my $json = $self->{json} ||=
1278 eval { require JSON::XS; JSON::XS->new->utf8 }
1279 || do { require JSON; JSON->new->utf8 };
1126 1280
1127 my $data; 1281 my $data;
1128 my $rbuf = \$self->{rbuf}; 1282 my $rbuf = \$self->{rbuf};
1129 1283
1130 my $json = $self->{json} ||= JSON->new->utf8;
1131
1132 sub { 1284 sub {
1133 my $ref = $json->incr_parse ($self->{rbuf}); 1285 my $ref = eval { $json->incr_parse ($self->{rbuf}) };
1134 1286
1135 if ($ref) { 1287 if ($ref) {
1136 $self->{rbuf} = $json->incr_text; 1288 $self->{rbuf} = $json->incr_text;
1137 $json->incr_text = ""; 1289 $json->incr_text = "";
1138 $cb->($self, $ref); 1290 $cb->($self, $ref);
1139 1291
1140 1 1292 1
1293 } elsif ($@) {
1294 # error case
1295 $json->incr_skip;
1296
1297 $self->{rbuf} = $json->incr_text;
1298 $json->incr_text = "";
1299
1300 $self->_error (&Errno::EBADMSG);
1301
1302 ()
1141 } else { 1303 } else {
1142 $self->{rbuf} = ""; 1304 $self->{rbuf} = "";
1305
1143 () 1306 ()
1144 } 1307 }
1145 } 1308 }
1146}; 1309};
1147 1310
1224Note that AnyEvent::Handle will automatically C<start_read> for you when 1387Note that AnyEvent::Handle will automatically C<start_read> for you when
1225you change the C<on_read> callback or push/unshift a read callback, and it 1388you change the C<on_read> callback or push/unshift a read callback, and it
1226will automatically C<stop_read> for you when neither C<on_read> is set nor 1389will automatically C<stop_read> for you when neither C<on_read> is set nor
1227there are any read requests in the queue. 1390there are any read requests in the queue.
1228 1391
1392These methods will have no effect when in TLS mode (as TLS doesn't support
1393half-duplex connections).
1394
1229=cut 1395=cut
1230 1396
1231sub stop_read { 1397sub stop_read {
1232 my ($self) = @_; 1398 my ($self) = @_;
1233 1399
1234 delete $self->{_rw}; 1400 delete $self->{_rw} unless $self->{tls};
1235} 1401}
1236 1402
1237sub start_read { 1403sub start_read {
1238 my ($self) = @_; 1404 my ($self) = @_;
1239 1405
1240 unless ($self->{_rw} || $self->{_eof}) { 1406 unless ($self->{_rw} || $self->{_eof}) {
1241 Scalar::Util::weaken $self; 1407 Scalar::Util::weaken $self;
1242 1408
1243 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { 1409 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub {
1244 my $rbuf = $self->{filter_r} ? \my $buf : \$self->{rbuf}; 1410 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1245 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 1411 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf;
1246 1412
1247 if ($len > 0) { 1413 if ($len > 0) {
1248 $self->{_activity} = AnyEvent->now; 1414 $self->{_activity} = AnyEvent->now;
1249 1415
1250 $self->{filter_r} 1416 if ($self->{tls}) {
1251 ? $self->{filter_r}($self, $rbuf) 1417 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
1252 : $self->{_in_drain} || $self->_drain_rbuf; 1418
1419 &_dotls ($self);
1420 } else {
1421 $self->_drain_rbuf unless $self->{_in_drain};
1422 }
1253 1423
1254 } elsif (defined $len) { 1424 } elsif (defined $len) {
1255 delete $self->{_rw}; 1425 delete $self->{_rw};
1256 $self->{_eof} = 1; 1426 $self->{_eof} = 1;
1257 $self->_drain_rbuf unless $self->{_in_drain}; 1427 $self->_drain_rbuf unless $self->{_in_drain};
1261 } 1431 }
1262 }); 1432 });
1263 } 1433 }
1264} 1434}
1265 1435
1436our $ERROR_SYSCALL;
1437our $ERROR_WANT_READ;
1438
1439sub _tls_error {
1440 my ($self, $err) = @_;
1441
1442 return $self->_error ($!, 1)
1443 if $err == Net::SSLeay::ERROR_SYSCALL ();
1444
1445 my $err =Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ());
1446
1447 # reduce error string to look less scary
1448 $err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /;
1449
1450 if ($self->{_on_starttls}) {
1451 (delete $self->{_on_starttls})->($self, undef, $err);
1452 &_freetls;
1453 } else {
1454 &_freetls;
1455 $self->_error (&Errno::EPROTO, 1, $err);
1456 }
1457}
1458
1459# poll the write BIO and send the data if applicable
1460# also decode read data if possible
1461# this is basiclaly our TLS state machine
1462# more efficient implementations are possible with openssl,
1463# but not with the buggy and incomplete Net::SSLeay.
1266sub _dotls { 1464sub _dotls {
1267 my ($self) = @_; 1465 my ($self) = @_;
1268 1466
1269 my $buf; 1467 my $tmp;
1270 1468
1271 if (length $self->{_tls_wbuf}) { 1469 if (length $self->{_tls_wbuf}) {
1272 while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { 1470 while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {
1273 substr $self->{_tls_wbuf}, 0, $len, ""; 1471 substr $self->{_tls_wbuf}, 0, $tmp, "";
1274 } 1472 }
1275 }
1276 1473
1474 $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
1475 return $self->_tls_error ($tmp)
1476 if $tmp != $ERROR_WANT_READ
1477 && ($tmp != $ERROR_SYSCALL || $!);
1478 }
1479
1480 while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
1481 unless (length $tmp) {
1482 $self->{_on_starttls}
1483 and (delete $self->{_on_starttls})->($self, undef, "EOF during handshake"); # ???
1484 &_freetls;
1485
1486 if ($self->{on_stoptls}) {
1487 $self->{on_stoptls}($self);
1488 return;
1489 } else {
1490 # let's treat SSL-eof as we treat normal EOF
1491 delete $self->{_rw};
1492 $self->{_eof} = 1;
1493 }
1494 }
1495
1496 $self->{_tls_rbuf} .= $tmp;
1497 $self->_drain_rbuf unless $self->{_in_drain};
1498 $self->{tls} or return; # tls session might have gone away in callback
1499 }
1500
1501 $tmp = Net::SSLeay::get_error ($self->{tls}, -1);
1502 return $self->_tls_error ($tmp)
1503 if $tmp != $ERROR_WANT_READ
1504 && ($tmp != $ERROR_SYSCALL || $!);
1505
1277 if (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) { 1506 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1278 $self->{wbuf} .= $buf; 1507 $self->{wbuf} .= $tmp;
1279 $self->_drain_wbuf; 1508 $self->_drain_wbuf;
1280 } 1509 }
1281 1510
1282 while (defined ($buf = Net::SSLeay::read ($self->{tls}))) { 1511 $self->{_on_starttls}
1283 if (length $buf) { 1512 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
1284 $self->{rbuf} .= $buf; 1513 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
1285 $self->_drain_rbuf unless $self->{_in_drain};
1286 } else {
1287 # let's treat SSL-eof as we treat normal EOF
1288 $self->{_eof} = 1;
1289 $self->_shutdown;
1290 return;
1291 }
1292 }
1293
1294 my $err = Net::SSLeay::get_error ($self->{tls}, -1);
1295
1296 if ($err!= Net::SSLeay::ERROR_WANT_READ ()) {
1297 if ($err == Net::SSLeay::ERROR_SYSCALL ()) {
1298 return $self->_error ($!, 1);
1299 } elsif ($err == Net::SSLeay::ERROR_SSL ()) {
1300 return $self->_error (&Errno::EIO, 1);
1301 }
1302
1303 # all others are fine for our purposes
1304 }
1305} 1514}
1306 1515
1307=item $handle->starttls ($tls[, $tls_ctx]) 1516=item $handle->starttls ($tls[, $tls_ctx])
1308 1517
1309Instead of starting TLS negotiation immediately when the AnyEvent::Handle 1518Instead of starting TLS negotiation immediately when the AnyEvent::Handle
1311C<starttls>. 1520C<starttls>.
1312 1521
1313The first argument is the same as the C<tls> constructor argument (either 1522The first argument is the same as the C<tls> constructor argument (either
1314C<"connect">, C<"accept"> or an existing Net::SSLeay object). 1523C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1315 1524
1316The second argument is the optional C<Net::SSLeay::CTX> object that is 1525The second argument is the optional C<AnyEvent::TLS> object that is used
1317used when AnyEvent::Handle has to create its own TLS connection object. 1526when AnyEvent::Handle has to create its own TLS connection object, or
1527a hash reference with C<< key => value >> pairs that will be used to
1528construct a new context.
1318 1529
1319The TLS connection object will end up in C<< $handle->{tls} >> after this 1530The TLS connection object will end up in C<< $handle->{tls} >>, the TLS
1320call and can be used or changed to your liking. Note that the handshake 1531context in C<< $handle->{tls_ctx} >> after this call and can be used or
1321might have already started when this function returns. 1532changed to your liking. Note that the handshake might have already started
1533when this function returns.
1322 1534
1535If it an error to start a TLS handshake more than once per
1536AnyEvent::Handle object (this is due to bugs in OpenSSL).
1537
1323=cut 1538=cut
1539
1540our %TLS_CACHE; #TODO not yet documented, should we?
1324 1541
1325sub starttls { 1542sub starttls {
1326 my ($self, $ssl, $ctx) = @_; 1543 my ($self, $ssl, $ctx) = @_;
1327 1544
1328 $self->stoptls; 1545 require Net::SSLeay;
1329 1546
1330 if ($ssl eq "accept") { 1547 Carp::croak "it is an error to call starttls more than once on an AnyEvent::Handle object"
1331 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1548 if $self->{tls};
1332 Net::SSLeay::set_accept_state ($ssl); 1549
1333 } elsif ($ssl eq "connect") { 1550 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
1334 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1551 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
1335 Net::SSLeay::set_connect_state ($ssl); 1552
1553 $ctx ||= $self->{tls_ctx};
1554
1555 if ("HASH" eq ref $ctx) {
1556 require AnyEvent::TLS;
1557
1558 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context
1559
1560 if ($ctx->{cache}) {
1561 my $key = $ctx+0;
1562 $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx;
1563 } else {
1564 $ctx = new AnyEvent::TLS %$ctx;
1565 }
1566 }
1336 } 1567
1337 1568 $self->{tls_ctx} = $ctx || TLS_CTX ();
1338 $self->{tls} = $ssl; 1569 $self->{tls} = $ssl = $self->{tls_ctx}->_get_session ($ssl, $self, $self->{peername});
1339 1570
1340 # basically, this is deep magic (because SSL_read should have the same issues) 1571 # basically, this is deep magic (because SSL_read should have the same issues)
1341 # but the openssl maintainers basically said: "trust us, it just works". 1572 # but the openssl maintainers basically said: "trust us, it just works".
1342 # (unfortunately, we have to hardcode constants because the abysmally misdesigned 1573 # (unfortunately, we have to hardcode constants because the abysmally misdesigned
1343 # and mismaintained ssleay-module doesn't even offer them). 1574 # and mismaintained ssleay-module doesn't even offer them).
1344 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html 1575 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html
1576 #
1577 # in short: this is a mess.
1578 #
1579 # note that we do not try to keep the length constant between writes as we are required to do.
1580 # we assume that most (but not all) of this insanity only applies to non-blocking cases,
1581 # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to
1582 # have identity issues in that area.
1345 Net::SSLeay::CTX_set_mode ($self->{tls}, 1583# Net::SSLeay::CTX_set_mode ($ssl,
1346 (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) 1584# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
1347 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); 1585# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
1586 Net::SSLeay::CTX_set_mode ($ssl, 1|2);
1348 1587
1349 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1588 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1350 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1589 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1351 1590
1352 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio}); 1591 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio});
1353 1592
1354 $self->{filter_w} = sub { 1593 $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
1355 $_[0]{_tls_wbuf} .= ${$_[1]}; 1594 if $self->{on_starttls};
1356 &_dotls; 1595
1357 }; 1596 &_dotls; # need to trigger the initial handshake
1358 $self->{filter_r} = sub { 1597 $self->start_read; # make sure we actually do read
1359 Net::SSLeay::BIO_write ($_[0]{_rbio}, ${$_[1]});
1360 &_dotls;
1361 };
1362} 1598}
1363 1599
1364=item $handle->stoptls 1600=item $handle->stoptls
1365 1601
1366Destroys the SSL connection, if any. Partial read or write data will be 1602Shuts down the SSL connection - this makes a proper EOF handshake by
1367lost. 1603sending a close notify to the other side, but since OpenSSL doesn't
1604support non-blocking shut downs, it is not possible to re-use the stream
1605afterwards.
1368 1606
1369=cut 1607=cut
1370 1608
1371sub stoptls { 1609sub stoptls {
1372 my ($self) = @_; 1610 my ($self) = @_;
1373 1611
1374 Net::SSLeay::free (delete $self->{tls}) if $self->{tls}; 1612 if ($self->{tls}) {
1613 Net::SSLeay::shutdown ($self->{tls});
1375 1614
1376 delete $self->{_rbio}; 1615 &_dotls;
1377 delete $self->{_wbio}; 1616
1378 delete $self->{_tls_wbuf}; 1617# # we don't give a shit. no, we do, but we can't. no...#d#
1379 delete $self->{filter_r}; 1618# # we, we... have to use openssl :/#d#
1380 delete $self->{filter_w}; 1619# &_freetls;#d#
1620 }
1621}
1622
1623sub _freetls {
1624 my ($self) = @_;
1625
1626 return unless $self->{tls};
1627
1628 $self->{tls_ctx}->_put_session (delete $self->{tls});
1629
1630 delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};
1381} 1631}
1382 1632
1383sub DESTROY { 1633sub DESTROY {
1384 my $self = shift; 1634 my ($self) = @_;
1385 1635
1386 $self->stoptls; 1636 &_freetls;
1387 1637
1388 my $linger = exists $self->{linger} ? $self->{linger} : 3600; 1638 my $linger = exists $self->{linger} ? $self->{linger} : 3600;
1389 1639
1390 if ($linger && length $self->{wbuf}) { 1640 if ($linger && length $self->{wbuf}) {
1391 my $fh = delete $self->{fh}; 1641 my $fh = delete $self->{fh};
1406 @linger = (); 1656 @linger = ();
1407 }); 1657 });
1408 } 1658 }
1409} 1659}
1410 1660
1661=item $handle->destroy
1662
1663Shuts down the handle object as much as possible - this call ensures that
1664no further callbacks will be invoked and as many resources as possible
1665will be freed. You must not call any methods on the object afterwards.
1666
1667Normally, you can just "forget" any references to an AnyEvent::Handle
1668object and it will simply shut down. This works in fatal error and EOF
1669callbacks, as well as code outside. It does I<NOT> work in a read or write
1670callback, so when you want to destroy the AnyEvent::Handle object from
1671within such an callback. You I<MUST> call C<< ->destroy >> explicitly in
1672that case.
1673
1674The handle might still linger in the background and write out remaining
1675data, as specified by the C<linger> option, however.
1676
1677=cut
1678
1679sub destroy {
1680 my ($self) = @_;
1681
1682 $self->DESTROY;
1683 %$self = ();
1684}
1685
1411=item AnyEvent::Handle::TLS_CTX 1686=item AnyEvent::Handle::TLS_CTX
1412 1687
1413This function creates and returns the Net::SSLeay::CTX object used by 1688This function creates and returns the AnyEvent::TLS object used by default
1414default for TLS mode. 1689for TLS mode.
1415 1690
1416The context is created like this: 1691The context is created by calling L<AnyEvent::TLS> without any arguments.
1417
1418 Net::SSLeay::load_error_strings;
1419 Net::SSLeay::SSLeay_add_ssl_algorithms;
1420 Net::SSLeay::randomize;
1421
1422 my $CTX = Net::SSLeay::CTX_new;
1423
1424 Net::SSLeay::CTX_set_options $CTX, Net::SSLeay::OP_ALL
1425 1692
1426=cut 1693=cut
1427 1694
1428our $TLS_CTX; 1695our $TLS_CTX;
1429 1696
1430sub TLS_CTX() { 1697sub TLS_CTX() {
1431 $TLS_CTX || do { 1698 $TLS_CTX ||= do {
1432 require Net::SSLeay; 1699 require AnyEvent::TLS;
1433 1700
1434 Net::SSLeay::load_error_strings (); 1701 new AnyEvent::TLS
1435 Net::SSLeay::SSLeay_add_ssl_algorithms ();
1436 Net::SSLeay::randomize ();
1437
1438 $TLS_CTX = Net::SSLeay::CTX_new ();
1439
1440 Net::SSLeay::CTX_set_options ($TLS_CTX, Net::SSLeay::OP_ALL ());
1441
1442 $TLS_CTX
1443 } 1702 }
1444} 1703}
1445 1704
1446=back 1705=back
1706
1707
1708=head1 NONFREQUENTLY ASKED QUESTIONS
1709
1710=over 4
1711
1712=item I C<undef> the AnyEvent::Handle reference inside my callback and
1713still get further invocations!
1714
1715That's because AnyEvent::Handle keeps a reference to itself when handling
1716read or write callbacks.
1717
1718It is only safe to "forget" the reference inside EOF or error callbacks,
1719from within all other callbacks, you need to explicitly call the C<<
1720->destroy >> method.
1721
1722=item I get different callback invocations in TLS mode/Why can't I pause
1723reading?
1724
1725Unlike, say, TCP, TLS connections do not consist of two independent
1726communication channels, one for each direction. Or put differently. The
1727read and write directions are not independent of each other: you cannot
1728write data unless you are also prepared to read, and vice versa.
1729
1730This can mean than, in TLS mode, you might get C<on_error> or C<on_eof>
1731callback invocations when you are not expecting any read data - the reason
1732is that AnyEvent::Handle always reads in TLS mode.
1733
1734During the connection, you have to make sure that you always have a
1735non-empty read-queue, or an C<on_read> watcher. At the end of the
1736connection (or when you no longer want to use it) you can call the
1737C<destroy> method.
1738
1739=item How do I read data until the other side closes the connection?
1740
1741If you just want to read your data into a perl scalar, the easiest way
1742to achieve this is by setting an C<on_read> callback that does nothing,
1743clearing the C<on_eof> callback and in the C<on_error> callback, the data
1744will be in C<$_[0]{rbuf}>:
1745
1746 $handle->on_read (sub { });
1747 $handle->on_eof (undef);
1748 $handle->on_error (sub {
1749 my $data = delete $_[0]{rbuf};
1750 undef $handle;
1751 });
1752
1753The reason to use C<on_error> is that TCP connections, due to latencies
1754and packets loss, might get closed quite violently with an error, when in
1755fact, all data has been received.
1756
1757It is usually better to use acknowledgements when transferring data,
1758to make sure the other side hasn't just died and you got the data
1759intact. This is also one reason why so many internet protocols have an
1760explicit QUIT command.
1761
1762=item I don't want to destroy the handle too early - how do I wait until
1763all data has been written?
1764
1765After writing your last bits of data, set the C<on_drain> callback
1766and destroy the handle in there - with the default setting of
1767C<low_water_mark> this will be called precisely when all data has been
1768written to the socket:
1769
1770 $handle->push_write (...);
1771 $handle->on_drain (sub {
1772 warn "all data submitted to the kernel\n";
1773 undef $handle;
1774 });
1775
1776If you just want to queue some data and then signal EOF to the other side,
1777consider using C<< ->push_shutdown >> instead.
1778
1779=item I want to contact a TLS/SSL server, I don't care about security.
1780
1781If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
1782simply connect to it and then create the AnyEvent::Handle with the C<tls>
1783parameter:
1784
1785 my $handle = new AnyEvent::Handle
1786 fh => $fh,
1787 tls => "connect",
1788 on_error => sub { ... };
1789
1790 $handle->push_write (...);
1791
1792=item I want to contact a TLS/SSL server, I do care about security.
1793
1794Then you #x##TODO#
1795
1796
1797
1798=back
1799
1447 1800
1448=head1 SUBCLASSING AnyEvent::Handle 1801=head1 SUBCLASSING AnyEvent::Handle
1449 1802
1450In many cases, you might want to subclass AnyEvent::Handle. 1803In many cases, you might want to subclass AnyEvent::Handle.
1451 1804

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines