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.67 by root, Fri Jun 6 15:33:10 2008 UTC vs.
Revision 1.134 by root, Fri Jul 3 00:09:04 2009 UTC

1package AnyEvent::Handle; 1package AnyEvent::Handle;
2 2
3no warnings; 3no warnings;
4use strict; 4use strict qw(subs vars);
5 5
6use AnyEvent (); 6use AnyEvent ();
7use AnyEvent::Util qw(WSAEWOULDBLOCK); 7use AnyEvent::Util qw(WSAEWOULDBLOCK);
8use Scalar::Util (); 8use Scalar::Util ();
9use Carp (); 9use Carp ();
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.15; 19our $VERSION = 4.45;
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 detcted, 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>).
124This sets the callback that is called when the write buffer becomes empty 149This sets the callback that is called when the write buffer becomes empty
125(or when the callback is set and the buffer is empty already). 150(or when the callback is set and the buffer is empty already).
126 151
127To append to the write buffer, use the C<< ->push_write >> method. 152To append to the write buffer, use the C<< ->push_write >> method.
128 153
154This callback is useful when you don't want to put all of your write data
155into the queue at once, for example, when you want to write the contents
156of some file to the socket you might not want to read the whole file into
157memory and push it into the queue, but instead only read more data from
158the file when the write queue becomes empty.
159
129=item timeout => $fractional_seconds 160=item timeout => $fractional_seconds
130 161
131If non-zero, then this enables an "inactivity" timeout: whenever this many 162If non-zero, then this enables an "inactivity" timeout: whenever this many
132seconds pass without a successful read or write on the underlying file 163seconds pass without a successful read or write on the underlying file
133handle, 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
134missing, an C<ETIMEDOUT> error will be raised). 165missing, a non-fatal C<ETIMEDOUT> error will be raised).
135 166
136Note 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
137any 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
138idle then you should disable the timout temporarily or ignore the timeout 169idle then you should disable the timout temporarily or ignore the timeout
139in the C<on_timeout> callback. 170in the C<on_timeout> callback, in which case AnyEvent::Handle will simply
171restart the timeout.
140 172
141Zero (the default) disables this timeout. 173Zero (the default) disables this timeout.
142 174
143=item on_timeout => $cb->($handle) 175=item on_timeout => $cb->($handle)
144 176
148 180
149=item rbuf_max => <bytes> 181=item rbuf_max => <bytes>
150 182
151If 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>)
152when 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
153avoid denial-of-service attacks. 185avoid some forms of denial-of-service attacks.
154 186
155For example, a server accepting connections from untrusted sources should 187For example, a server accepting connections from untrusted sources should
156be 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
157(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
158amount 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
159isn't finished). 191isn't finished).
160 192
193=item autocork => <boolean>
194
195When disabled (the default), then C<push_write> will try to immediately
196write the data to the handle, if possible. This avoids having to register
197a write watcher and wait for the next event loop iteration, but can
198be inefficient if you write multiple small chunks (on the wire, this
199disadvantage is usually avoided by your kernel's nagle algorithm, see
200C<no_delay>, but this option can save costly syscalls).
201
202When enabled, then writes will always be queued till the next event loop
203iteration. This is efficient when you do many small writes per iteration,
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.
206
207=item no_delay => <boolean>
208
209When doing small writes on sockets, your operating system kernel might
210wait a bit for more data before actually sending it out. This is called
211the Nagle algorithm, and usually it is beneficial.
212
213In some situations you want as low a delay as possible, which can be
214accomplishd by setting this option to a true value.
215
216The default is your opertaing system's default behaviour (most likely
217enabled), this option explicitly enables or disables it, if possible.
218
161=item read_size => <bytes> 219=item read_size => <bytes>
162 220
163The 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
164during each (loop iteration). Default: C<8192>. 222try to read during each loop iteration, which affects memory
223requirements). Default: C<8192>.
165 224
166=item low_water_mark => <bytes> 225=item low_water_mark => <bytes>
167 226
168Sets 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
169buffer: 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
170considered empty. 229considered empty.
171 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
172=item linger => <seconds> 236=item linger => <seconds>
173 237
174If non-zero (default: C<3600>), then the destructor of the 238If non-zero (default: C<3600>), then the destructor of the
175AnyEvent::Handle object will check wether there is still outstanding write 239AnyEvent::Handle object will check whether there is still outstanding
176data 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
177will be reported (this mostly matches how the operating system treats 241socket. No errors will be reported (this mostly matches how the operating
178outstanding data at socket close time). 242system treats outstanding data at socket close time).
179 243
180This 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
181encoded. 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
254common name verification (see C<verify_cn> in L<AnyEvent::TLS>).
182 255
183=item tls => "accept" | "connect" | Net::SSLeay::SSL object 256=item tls => "accept" | "connect" | Net::SSLeay::SSL object
184 257
185When this parameter is given, it enables TLS (SSL) mode, that means it 258When this parameter is given, it enables TLS (SSL) mode, that means
186will start making tls handshake and will transparently encrypt/decrypt 259AnyEvent will start a TLS handshake as soon as the conenction has been
187data. 260established and will transparently encrypt/decrypt data afterwards.
261
262All TLS protocol errors will be signalled as C<EPROTO>, with an
263appropriate error message.
188 264
189TLS mode requires Net::SSLeay to be installed (it will be loaded 265TLS mode requires Net::SSLeay to be installed (it will be loaded
190automatically 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.
191 269
192For 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
193connection, use C<connect> mode. 271C<accept>, and for the TLS client side of a connection, use C<connect>
272mode.
194 273
195You can also provide your own TLS connection object, but you have 274You can also provide your own TLS connection object, but you have
196to 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>
197or 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
198AnyEvent::Handle. 277AnyEvent::Handle. Also, this module will take ownership of this connection
278object.
199 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
200See 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.
201 290
202=item tls_ctx => $ssl_ctx 291=item tls_ctx => $anyevent_tls
203 292
204Use 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
205(unless a connection object was specified directly). If this parameter is 294(unless a connection object was specified directly). If this parameter is
206missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. 295missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>.
207 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
208=item json => JSON or JSON::XS object 301=item json => JSON or JSON::XS object
209 302
210This is the json coder object used by the C<json> read and write types. 303This is the json coder object used by the C<json> read and write types.
211 304
212If you don't supply it, then AnyEvent::Handle will create and use a 305If you don't supply it, then AnyEvent::Handle will create and use a
213suitable one, which will write and expect UTF-8 encoded JSON texts. 306suitable one (on demand), which will write and expect UTF-8 encoded JSON
307texts.
214 308
215Note that you are responsible to depend on the JSON module if you want to 309Note that you are responsible to depend on the JSON module if you want to
216use this functionality, as AnyEvent does not have a dependency itself. 310use this functionality, as AnyEvent does not have a dependency itself.
217 311
218=item filter_r => $cb
219
220=item filter_w => $cb
221
222These exist, but are undocumented at this time.
223
224=back 312=back
225 313
226=cut 314=cut
227 315
228sub new { 316sub new {
229 my $class = shift; 317 my $class = shift;
230
231 my $self = bless { @_ }, $class; 318 my $self = bless { @_ }, $class;
232 319
233 $self->{fh} or Carp::croak "mandatory argument fh is missing"; 320 $self->{fh} or Carp::croak "mandatory argument fh is missing";
234 321
235 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 322 AnyEvent::Util::fh_nonblocking $self->{fh}, 1;
236
237 if ($self->{tls}) {
238 require Net::SSLeay;
239 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx});
240 }
241 323
242 $self->{_activity} = AnyEvent->now; 324 $self->{_activity} = AnyEvent->now;
243 $self->_timeout; 325 $self->_timeout;
244 326
327 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay};
328
329 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
330 if $self->{tls};
331
245 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain}; 332 $self->on_drain (delete $self->{on_drain}) if exists $self->{on_drain};
246 333
247 $self->start_read 334 $self->start_read
248 if $self->{on_read}; 335 if $self->{on_read};
249 336
250 $self 337 $self->{fh} && $self
251} 338}
252 339
253sub _shutdown { 340sub _shutdown {
254 my ($self) = @_; 341 my ($self) = @_;
255 342
256 delete $self->{_tw}; 343 delete @$self{qw(_tw _rw _ww fh wbuf on_read _queue)};
257 delete $self->{_rw}; 344 $self->{_eof} = 1; # tell starttls et. al to stop trying
258 delete $self->{_ww};
259 delete $self->{fh};
260 345
261 $self->stoptls; 346 &_freetls;
262} 347}
263 348
264sub _error { 349sub _error {
265 my ($self, $errno, $fatal) = @_; 350 my ($self, $errno, $fatal, $message) = @_;
266 351
267 $self->_shutdown 352 $self->_shutdown
268 if $fatal; 353 if $fatal;
269 354
270 $! = $errno; 355 $! = $errno;
356 $message ||= "$!";
271 357
272 if ($self->{on_error}) { 358 if ($self->{on_error}) {
273 $self->{on_error}($self, $fatal); 359 $self->{on_error}($self, $fatal, $message);
274 } else { 360 } elsif ($self->{fh}) {
275 Carp::croak "AnyEvent::Handle uncaught error: $!"; 361 Carp::croak "AnyEvent::Handle uncaught error: $message";
276 } 362 }
277} 363}
278 364
279=item $fh = $handle->fh 365=item $fh = $handle->fh
280 366
281This method returns the file handle of the L<AnyEvent::Handle> object. 367This method returns the file handle used to create the L<AnyEvent::Handle> object.
282 368
283=cut 369=cut
284 370
285sub fh { $_[0]{fh} } 371sub fh { $_[0]{fh} }
286 372
304 $_[0]{on_eof} = $_[1]; 390 $_[0]{on_eof} = $_[1];
305} 391}
306 392
307=item $handle->on_timeout ($cb) 393=item $handle->on_timeout ($cb)
308 394
309Replace the current C<on_timeout> callback, or disables the callback 395Replace the current C<on_timeout> callback, or disables the callback (but
310(but not the timeout) if C<$cb> = C<undef>. See C<timeout> constructor 396not the timeout) if C<$cb> = C<undef>. See the C<timeout> constructor
311argument. 397argument and method.
312 398
313=cut 399=cut
314 400
315sub on_timeout { 401sub on_timeout {
316 $_[0]{on_timeout} = $_[1]; 402 $_[0]{on_timeout} = $_[1];
403}
404
405=item $handle->autocork ($boolean)
406
407Enables or disables the current autocork behaviour (see C<autocork>
408constructor argument). Changes will only take effect on the next write.
409
410=cut
411
412sub autocork {
413 $_[0]{autocork} = $_[1];
414}
415
416=item $handle->no_delay ($boolean)
417
418Enables or disables the C<no_delay> setting (see constructor argument of
419the same name for details).
420
421=cut
422
423sub no_delay {
424 $_[0]{no_delay} = $_[1];
425
426 eval {
427 local $SIG{__DIE__};
428 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1];
429 };
317} 430}
318 431
319############################################################################# 432#############################################################################
320 433
321=item $handle->timeout ($seconds) 434=item $handle->timeout ($seconds)
399 my ($self, $cb) = @_; 512 my ($self, $cb) = @_;
400 513
401 $self->{on_drain} = $cb; 514 $self->{on_drain} = $cb;
402 515
403 $cb->($self) 516 $cb->($self)
404 if $cb && $self->{low_water_mark} >= length $self->{wbuf}; 517 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
405} 518}
406 519
407=item $handle->push_write ($data) 520=item $handle->push_write ($data)
408 521
409Queues the given scalar to be written. You can push as much data as you 522Queues the given scalar to be written. You can push as much data as you
426 substr $self->{wbuf}, 0, $len, ""; 539 substr $self->{wbuf}, 0, $len, "";
427 540
428 $self->{_activity} = AnyEvent->now; 541 $self->{_activity} = AnyEvent->now;
429 542
430 $self->{on_drain}($self) 543 $self->{on_drain}($self)
431 if $self->{low_water_mark} >= length $self->{wbuf} 544 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
432 && $self->{on_drain}; 545 && $self->{on_drain};
433 546
434 delete $self->{_ww} unless length $self->{wbuf}; 547 delete $self->{_ww} unless length $self->{wbuf};
435 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 548 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) {
436 $self->_error ($!, 1); 549 $self->_error ($!, 1);
437 } 550 }
438 }; 551 };
439 552
440 # try to write data immediately 553 # try to write data immediately
441 $cb->(); 554 $cb->() unless $self->{autocork};
442 555
443 # if still data left in wbuf, we need to poll 556 # if still data left in wbuf, we need to poll
444 $self->{_ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb) 557 $self->{_ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb)
445 if length $self->{wbuf}; 558 if length $self->{wbuf};
446 }; 559 };
460 573
461 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") 574 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write")
462 ->($self, @_); 575 ->($self, @_);
463 } 576 }
464 577
465 if ($self->{filter_w}) { 578 if ($self->{tls}) {
466 $self->{filter_w}($self, \$_[0]); 579 $self->{_tls_wbuf} .= $_[0];
580
581 &_dotls ($self);
467 } else { 582 } else {
468 $self->{wbuf} .= $_[0]; 583 $self->{wbuf} .= $_[0];
469 $self->_drain_wbuf; 584 $self->_drain_wbuf;
470 } 585 }
471} 586}
488=cut 603=cut
489 604
490register_write_type netstring => sub { 605register_write_type netstring => sub {
491 my ($self, $string) = @_; 606 my ($self, $string) = @_;
492 607
493 sprintf "%d:%s,", (length $string), $string 608 (length $string) . ":$string,"
494}; 609};
495 610
496=item packstring => $format, $data 611=item packstring => $format, $data
497 612
498An octet string prefixed with an encoded length. The encoding C<$format> 613An octet string prefixed with an encoded length. The encoding C<$format>
564 pack "w/a*", Storable::nfreeze ($ref) 679 pack "w/a*", Storable::nfreeze ($ref)
565}; 680};
566 681
567=back 682=back
568 683
684=item $handle->push_shutdown
685
686Sometimes you know you want to close the socket after writing your data
687before it was actually written. One way to do that is to replace your
688C<on_drain> handler by a callback that shuts down the socket. This method
689is a shorthand for just that, and replaces the C<on_drain> callback with:
690
691 sub { shutdown $_[0]{fh}, 1 } # for push_shutdown
692
693This simply shuts down the write side and signals an EOF condition to the
694the peer.
695
696You can rely on the normal read queue and C<on_eof> handling
697afterwards. This is the cleanest way to close a connection.
698
699=cut
700
701sub push_shutdown {
702 $_[0]->{on_drain} = sub { shutdown $_[0]{fh}, 1 };
703}
704
569=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args) 705=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args)
570 706
571This function (not method) lets you add your own types to C<push_write>. 707This function (not method) lets you add your own types to C<push_write>.
572Whenever the given C<type> is used, C<push_write> will invoke the code 708Whenever the given C<type> is used, C<push_write> will invoke the code
573reference with the handle object and the remaining arguments. 709reference with the handle object and the remaining arguments.
593ways, the "simple" way, using only C<on_read> and the "complex" way, using 729ways, the "simple" way, using only C<on_read> and the "complex" way, using
594a queue. 730a queue.
595 731
596In the simple case, you just install an C<on_read> callback and whenever 732In the simple case, you just install an C<on_read> callback and whenever
597new data arrives, it will be called. You can then remove some data (if 733new data arrives, it will be called. You can then remove some data (if
598enough is there) from the read buffer (C<< $handle->rbuf >>) if you want 734enough is there) from the read buffer (C<< $handle->rbuf >>). Or you cna
599or not. 735leave the data there if you want to accumulate more (e.g. when only a
736partial message has been received so far).
600 737
601In the more complex case, you want to queue multiple callbacks. In this 738In the more complex case, you want to queue multiple callbacks. In this
602case, AnyEvent::Handle will call the first queued callback each time new 739case, AnyEvent::Handle will call the first queued callback each time new
603data arrives (also the first time it is queued) and removes it when it has 740data arrives (also the first time it is queued) and removes it when it has
604done its job (see C<push_read>, below). 741done its job (see C<push_read>, below).
622 # handle xml 759 # handle xml
623 }); 760 });
624 }); 761 });
625 }); 762 });
626 763
627Example 2: Implement a client for a protocol that replies either with 764Example 2: Implement a client for a protocol that replies either with "OK"
628"OK" and another line or "ERROR" for one request, and 64 bytes for the 765and another line or "ERROR" for the first request that is sent, and 64
629second request. Due tot he availability of a full queue, we can just 766bytes for the second request. Due to the availability of a queue, we can
630pipeline sending both requests and manipulate the queue as necessary in 767just pipeline sending both requests and manipulate the queue as necessary
631the callbacks: 768in the callbacks.
632 769
633 # request one 770When the first callback is called and sees an "OK" response, it will
771C<unshift> another line-read. This line-read will be queued I<before> the
77264-byte chunk callback.
773
774 # request one, returns either "OK + extra line" or "ERROR"
634 $handle->push_write ("request 1\015\012"); 775 $handle->push_write ("request 1\015\012");
635 776
636 # we expect "ERROR" or "OK" as response, so push a line read 777 # we expect "ERROR" or "OK" as response, so push a line read
637 $handle->push_read (line => sub { 778 $handle->push_read (line => sub {
638 # if we got an "OK", we have to _prepend_ another line, 779 # if we got an "OK", we have to _prepend_ another line,
645 ... 786 ...
646 }); 787 });
647 } 788 }
648 }); 789 });
649 790
650 # request two 791 # request two, simply returns 64 octets
651 $handle->push_write ("request 2\015\012"); 792 $handle->push_write ("request 2\015\012");
652 793
653 # simply read 64 bytes, always 794 # simply read 64 bytes, always
654 $handle->push_read (chunk => 64, sub { 795 $handle->push_read (chunk => 64, sub {
655 my $response = $_[1]; 796 my $response = $_[1];
667 808
668 if ( 809 if (
669 defined $self->{rbuf_max} 810 defined $self->{rbuf_max}
670 && $self->{rbuf_max} < length $self->{rbuf} 811 && $self->{rbuf_max} < length $self->{rbuf}
671 ) { 812 ) {
672 return $self->_error (&Errno::ENOSPC, 1); 813 $self->_error (&Errno::ENOSPC, 1), return;
673 } 814 }
674 815
675 while () { 816 while () {
676 no strict 'refs'; 817 # we need to use a separate tls read buffer, as we must not receive data while
818 # we are draining the buffer, and this can only happen with TLS.
819 $self->{rbuf} .= delete $self->{_tls_rbuf} if exists $self->{_tls_rbuf};
677 820
678 my $len = length $self->{rbuf}; 821 my $len = length $self->{rbuf};
679 822
680 if (my $cb = shift @{ $self->{_queue} }) { 823 if (my $cb = shift @{ $self->{_queue} }) {
681 unless ($cb->($self)) { 824 unless ($cb->($self)) {
682 if ($self->{_eof}) { 825 if ($self->{_eof}) {
683 # no progress can be made (not enough data and no data forthcoming) 826 # no progress can be made (not enough data and no data forthcoming)
684 $self->_error (&Errno::EPIPE, 1), last; 827 $self->_error (&Errno::EPIPE, 1), return;
685 } 828 }
686 829
687 unshift @{ $self->{_queue} }, $cb; 830 unshift @{ $self->{_queue} }, $cb;
688 last; 831 last;
689 } 832 }
697 && !@{ $self->{_queue} } # and the queue is still empty 840 && !@{ $self->{_queue} } # and the queue is still empty
698 && $self->{on_read} # but we still have on_read 841 && $self->{on_read} # but we still have on_read
699 ) { 842 ) {
700 # no further data will arrive 843 # no further data will arrive
701 # so no progress can be made 844 # so no progress can be made
702 $self->_error (&Errno::EPIPE, 1), last 845 $self->_error (&Errno::EPIPE, 1), return
703 if $self->{_eof}; 846 if $self->{_eof};
704 847
705 last; # more data might arrive 848 last; # more data might arrive
706 } 849 }
707 } else { 850 } else {
708 # read side becomes idle 851 # read side becomes idle
709 delete $self->{_rw}; 852 delete $self->{_rw} unless $self->{tls};
710 last; 853 last;
711 } 854 }
712 } 855 }
713 856
857 if ($self->{_eof}) {
858 if ($self->{on_eof}) {
714 $self->{on_eof}($self) 859 $self->{on_eof}($self)
715 if $self->{_eof} && $self->{on_eof}; 860 } else {
861 $self->_error (0, 1);
862 }
863 }
716 864
717 # may need to restart read watcher 865 # may need to restart read watcher
718 unless ($self->{_rw}) { 866 unless ($self->{_rw}) {
719 $self->start_read 867 $self->start_read
720 if $self->{on_read} || @{ $self->{_queue} }; 868 if $self->{on_read} || @{ $self->{_queue} };
738 886
739=item $handle->rbuf 887=item $handle->rbuf
740 888
741Returns the read buffer (as a modifiable lvalue). 889Returns the read buffer (as a modifiable lvalue).
742 890
743You can access the read buffer directly as the C<< ->{rbuf} >> member, if 891You can access the read buffer directly as the C<< ->{rbuf} >>
744you want. 892member, if you want. However, the only operation allowed on the
893read buffer (apart from looking at it) is removing data from its
894beginning. Otherwise modifying or appending to it is not allowed and will
895lead to hard-to-track-down bugs.
745 896
746NOTE: The read buffer should only be used or modified if the C<on_read>, 897NOTE: The read buffer should only be used or modified if the C<on_read>,
747C<push_read> or C<unshift_read> methods are used. The other read methods 898C<push_read> or C<unshift_read> methods are used. The other read methods
748automatically manage the read buffer. 899automatically manage the read buffer.
749 900
846 $cb->($_[0], substr $_[0]{rbuf}, 0, $len, ""); 997 $cb->($_[0], substr $_[0]{rbuf}, 0, $len, "");
847 1 998 1
848 } 999 }
849}; 1000};
850 1001
851# compatibility with older API
852sub push_read_chunk {
853 $_[0]->push_read (chunk => $_[1], $_[2]);
854}
855
856sub unshift_read_chunk {
857 $_[0]->unshift_read (chunk => $_[1], $_[2]);
858}
859
860=item line => [$eol, ]$cb->($handle, $line, $eol) 1002=item line => [$eol, ]$cb->($handle, $line, $eol)
861 1003
862The callback will be called only once a full line (including the end of 1004The callback will be called only once a full line (including the end of
863line marker, C<$eol>) has been read. This line (excluding the end of line 1005line marker, C<$eol>) has been read. This line (excluding the end of line
864marker) will be passed to the callback as second argument (C<$line>), and 1006marker) will be passed to the callback as second argument (C<$line>), and
879=cut 1021=cut
880 1022
881register_read_type line => sub { 1023register_read_type line => sub {
882 my ($self, $cb, $eol) = @_; 1024 my ($self, $cb, $eol) = @_;
883 1025
884 $eol = qr|(\015?\012)| if @_ < 3; 1026 if (@_ < 3) {
1027 # this is more than twice as fast as the generic code below
1028 sub {
1029 $_[0]{rbuf} =~ s/^([^\015\012]*)(\015?\012)// or return;
1030
1031 $cb->($_[0], $1, $2);
1032 1
1033 }
1034 } else {
885 $eol = quotemeta $eol unless ref $eol; 1035 $eol = quotemeta $eol unless ref $eol;
886 $eol = qr|^(.*?)($eol)|s; 1036 $eol = qr|^(.*?)($eol)|s;
887 1037
888 sub { 1038 sub {
889 $_[0]{rbuf} =~ s/$eol// or return; 1039 $_[0]{rbuf} =~ s/$eol// or return;
890 1040
891 $cb->($_[0], $1, $2); 1041 $cb->($_[0], $1, $2);
1042 1
892 1 1043 }
893 } 1044 }
894}; 1045};
895
896# compatibility with older API
897sub push_read_line {
898 my $self = shift;
899 $self->push_read (line => @_);
900}
901
902sub unshift_read_line {
903 my $self = shift;
904 $self->unshift_read (line => @_);
905}
906 1046
907=item regex => $accept[, $reject[, $skip], $cb->($handle, $data) 1047=item regex => $accept[, $reject[, $skip], $cb->($handle, $data)
908 1048
909Makes a regex match against the regex object C<$accept> and returns 1049Makes a regex match against the regex object C<$accept> and returns
910everything up to and including the match. 1050everything up to and including the match.
1015An octet string prefixed with an encoded length. The encoding C<$format> 1155An octet string prefixed with an encoded length. The encoding C<$format>
1016uses the same format as a Perl C<pack> format, but must specify a single 1156uses the same format as a Perl C<pack> format, but must specify a single
1017integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an 1157integer only (only one of C<cCsSlLqQiInNvVjJw> is allowed, plus an
1018optional C<!>, C<< < >> or C<< > >> modifier). 1158optional C<!>, C<< < >> or C<< > >> modifier).
1019 1159
1020DNS over TCP uses a prefix of C<n>, EPP uses a prefix of C<N>. 1160For example, DNS over TCP uses a prefix of C<n> (2 octet network order),
1161EPP uses a prefix of C<N> (4 octtes).
1021 1162
1022Example: read a block of data prefixed by its length in BER-encoded 1163Example: read a block of data prefixed by its length in BER-encoded
1023format (very efficient). 1164format (very efficient).
1024 1165
1025 $handle->push_read (packstring => "w", sub { 1166 $handle->push_read (packstring => "w", sub {
1031register_read_type packstring => sub { 1172register_read_type packstring => sub {
1032 my ($self, $cb, $format) = @_; 1173 my ($self, $cb, $format) = @_;
1033 1174
1034 sub { 1175 sub {
1035 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method 1176 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method
1036 defined (my $len = eval { unpack $format, $_[0]->{rbuf} }) 1177 defined (my $len = eval { unpack $format, $_[0]{rbuf} })
1037 or return; 1178 or return;
1038 1179
1180 $format = length pack $format, $len;
1181
1182 # bypass unshift if we already have the remaining chunk
1183 if ($format + $len <= length $_[0]{rbuf}) {
1184 my $data = substr $_[0]{rbuf}, $format, $len;
1185 substr $_[0]{rbuf}, 0, $format + $len, "";
1186 $cb->($_[0], $data);
1187 } else {
1039 # remove prefix 1188 # remove prefix
1040 substr $_[0]->{rbuf}, 0, (length pack $format, $len), ""; 1189 substr $_[0]{rbuf}, 0, $format, "";
1041 1190
1042 # read rest 1191 # read remaining chunk
1043 $_[0]->unshift_read (chunk => $len, $cb); 1192 $_[0]->unshift_read (chunk => $len, $cb);
1193 }
1044 1194
1045 1 1195 1
1046 } 1196 }
1047}; 1197};
1048 1198
1049=item json => $cb->($handle, $hash_or_arrayref) 1199=item json => $cb->($handle, $hash_or_arrayref)
1050 1200
1051Reads a JSON object or array, decodes it and passes it to the callback. 1201Reads a JSON object or array, decodes it and passes it to the
1202callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1052 1203
1053If a C<json> object was passed to the constructor, then that will be used 1204If a C<json> object was passed to the constructor, then that will be used
1054for the final decode, otherwise it will create a JSON coder expecting UTF-8. 1205for the final decode, otherwise it will create a JSON coder expecting UTF-8.
1055 1206
1056This read type uses the incremental parser available with JSON version 1207This read type uses the incremental parser available with JSON version
1073 my $rbuf = \$self->{rbuf}; 1224 my $rbuf = \$self->{rbuf};
1074 1225
1075 my $json = $self->{json} ||= JSON->new->utf8; 1226 my $json = $self->{json} ||= JSON->new->utf8;
1076 1227
1077 sub { 1228 sub {
1078 my $ref = $json->incr_parse ($self->{rbuf}); 1229 my $ref = eval { $json->incr_parse ($self->{rbuf}) };
1079 1230
1080 if ($ref) { 1231 if ($ref) {
1081 $self->{rbuf} = $json->incr_text; 1232 $self->{rbuf} = $json->incr_text;
1082 $json->incr_text = ""; 1233 $json->incr_text = "";
1083 $cb->($self, $ref); 1234 $cb->($self, $ref);
1084 1235
1085 1 1236 1
1237 } elsif ($@) {
1238 # error case
1239 $json->incr_skip;
1240
1241 $self->{rbuf} = $json->incr_text;
1242 $json->incr_text = "";
1243
1244 $self->_error (&Errno::EBADMSG);
1245
1246 ()
1086 } else { 1247 } else {
1087 $self->{rbuf} = ""; 1248 $self->{rbuf} = "";
1249
1088 () 1250 ()
1089 } 1251 }
1090 } 1252 }
1091}; 1253};
1092 1254
1105 1267
1106 require Storable; 1268 require Storable;
1107 1269
1108 sub { 1270 sub {
1109 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method 1271 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method
1110 defined (my $len = eval { unpack "w", $_[0]->{rbuf} }) 1272 defined (my $len = eval { unpack "w", $_[0]{rbuf} })
1111 or return; 1273 or return;
1112 1274
1275 my $format = length pack "w", $len;
1276
1277 # bypass unshift if we already have the remaining chunk
1278 if ($format + $len <= length $_[0]{rbuf}) {
1279 my $data = substr $_[0]{rbuf}, $format, $len;
1280 substr $_[0]{rbuf}, 0, $format + $len, "";
1281 $cb->($_[0], Storable::thaw ($data));
1282 } else {
1113 # remove prefix 1283 # remove prefix
1114 substr $_[0]->{rbuf}, 0, (length pack "w", $len), ""; 1284 substr $_[0]{rbuf}, 0, $format, "";
1115 1285
1116 # read rest 1286 # read remaining chunk
1117 $_[0]->unshift_read (chunk => $len, sub { 1287 $_[0]->unshift_read (chunk => $len, sub {
1118 if (my $ref = eval { Storable::thaw ($_[1]) }) { 1288 if (my $ref = eval { Storable::thaw ($_[1]) }) {
1119 $cb->($_[0], $ref); 1289 $cb->($_[0], $ref);
1120 } else { 1290 } else {
1121 $self->_error (&Errno::EBADMSG); 1291 $self->_error (&Errno::EBADMSG);
1292 }
1122 } 1293 });
1123 }); 1294 }
1295
1296 1
1124 } 1297 }
1125}; 1298};
1126 1299
1127=back 1300=back
1128 1301
1158Note that AnyEvent::Handle will automatically C<start_read> for you when 1331Note that AnyEvent::Handle will automatically C<start_read> for you when
1159you change the C<on_read> callback or push/unshift a read callback, and it 1332you change the C<on_read> callback or push/unshift a read callback, and it
1160will automatically C<stop_read> for you when neither C<on_read> is set nor 1333will automatically C<stop_read> for you when neither C<on_read> is set nor
1161there are any read requests in the queue. 1334there are any read requests in the queue.
1162 1335
1336These methods will have no effect when in TLS mode (as TLS doesn't support
1337half-duplex connections).
1338
1163=cut 1339=cut
1164 1340
1165sub stop_read { 1341sub stop_read {
1166 my ($self) = @_; 1342 my ($self) = @_;
1167 1343
1168 delete $self->{_rw}; 1344 delete $self->{_rw} unless $self->{tls};
1169} 1345}
1170 1346
1171sub start_read { 1347sub start_read {
1172 my ($self) = @_; 1348 my ($self) = @_;
1173 1349
1174 unless ($self->{_rw} || $self->{_eof}) { 1350 unless ($self->{_rw} || $self->{_eof}) {
1175 Scalar::Util::weaken $self; 1351 Scalar::Util::weaken $self;
1176 1352
1177 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { 1353 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub {
1178 my $rbuf = $self->{filter_r} ? \my $buf : \$self->{rbuf}; 1354 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1179 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 1355 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf;
1180 1356
1181 if ($len > 0) { 1357 if ($len > 0) {
1182 $self->{_activity} = AnyEvent->now; 1358 $self->{_activity} = AnyEvent->now;
1183 1359
1184 $self->{filter_r} 1360 if ($self->{tls}) {
1185 ? $self->{filter_r}($self, $rbuf) 1361 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
1186 : $self->{_in_drain} || $self->_drain_rbuf; 1362
1363 &_dotls ($self);
1364 } else {
1365 $self->_drain_rbuf unless $self->{_in_drain};
1366 }
1187 1367
1188 } elsif (defined $len) { 1368 } elsif (defined $len) {
1189 delete $self->{_rw}; 1369 delete $self->{_rw};
1190 $self->{_eof} = 1; 1370 $self->{_eof} = 1;
1191 $self->_drain_rbuf unless $self->{_in_drain}; 1371 $self->_drain_rbuf unless $self->{_in_drain};
1195 } 1375 }
1196 }); 1376 });
1197 } 1377 }
1198} 1378}
1199 1379
1380our $ERROR_SYSCALL;
1381our $ERROR_WANT_READ;
1382our $ERROR_ZERO_RETURN;
1383
1384sub _tls_error {
1385 my ($self, $err) = @_;
1386 warn "$err,$!\n";#d#
1387
1388 return $self->_error ($!, 1)
1389 if $err == Net::SSLeay::ERROR_SYSCALL ();
1390
1391 $self->_error (&Errno::EPROTO, 1,
1392 Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ()));
1393}
1394
1395# poll the write BIO and send the data if applicable
1396# also decode read data if possible
1397# this is basiclaly our TLS state machine
1398# more efficient implementations are possible with openssl,
1399# but not with the buggy and incomplete Net::SSLeay.
1200sub _dotls { 1400sub _dotls {
1201 my ($self) = @_; 1401 my ($self) = @_;
1202 1402
1203 my $buf; 1403 my $tmp;
1204 1404
1205 if (length $self->{_tls_wbuf}) { 1405 if (length $self->{_tls_wbuf}) {
1206 while ((my $len = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { 1406 while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) {
1207 substr $self->{_tls_wbuf}, 0, $len, ""; 1407 substr $self->{_tls_wbuf}, 0, $tmp, "";
1208 } 1408 }
1209 }
1210 1409
1410 $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
1411 return $self->_tls_error ($tmp)
1412 if $tmp != $ERROR_WANT_READ
1413 && ($tmp != $ERROR_SYSCALL || $!)
1414 && $tmp != $ERROR_ZERO_RETURN;
1415 }
1416
1417 while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
1418 unless (length $tmp) {
1419 # let's treat SSL-eof as we treat normal EOF
1420 delete $self->{_rw};
1421 $self->{_eof} = 1;
1422 &_freetls;
1423 }
1424
1425 $self->{_tls_rbuf} .= $tmp;
1426 $self->_drain_rbuf unless $self->{_in_drain};
1427 $self->{tls} or return; # tls session might have gone away in callback
1428 }
1429
1430 $tmp = Net::SSLeay::get_error ($self->{tls}, -1);
1431 return $self->_tls_error ($tmp)
1432 if $tmp != $ERROR_WANT_READ
1433 && ($tmp != $ERROR_SYSCALL || $!)
1434 && $tmp != $ERROR_ZERO_RETURN;
1435
1211 if (length ($buf = Net::SSLeay::BIO_read ($self->{_wbio}))) { 1436 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1212 $self->{wbuf} .= $buf; 1437 $self->{wbuf} .= $tmp;
1213 $self->_drain_wbuf; 1438 $self->_drain_wbuf;
1214 }
1215
1216 while (defined ($buf = Net::SSLeay::read ($self->{tls}))) {
1217 if (length $buf) {
1218 $self->{rbuf} .= $buf;
1219 $self->_drain_rbuf unless $self->{_in_drain};
1220 } else {
1221 # let's treat SSL-eof as we treat normal EOF
1222 $self->{_eof} = 1;
1223 $self->_shutdown;
1224 return;
1225 }
1226 }
1227
1228 my $err = Net::SSLeay::get_error ($self->{tls}, -1);
1229
1230 if ($err!= Net::SSLeay::ERROR_WANT_READ ()) {
1231 if ($err == Net::SSLeay::ERROR_SYSCALL ()) {
1232 return $self->_error ($!, 1);
1233 } elsif ($err == Net::SSLeay::ERROR_SSL ()) {
1234 return $self->_error (&Errno::EIO, 1);
1235 }
1236
1237 # all others are fine for our purposes
1238 } 1439 }
1239} 1440}
1240 1441
1241=item $handle->starttls ($tls[, $tls_ctx]) 1442=item $handle->starttls ($tls[, $tls_ctx])
1242 1443
1245C<starttls>. 1446C<starttls>.
1246 1447
1247The first argument is the same as the C<tls> constructor argument (either 1448The first argument is the same as the C<tls> constructor argument (either
1248C<"connect">, C<"accept"> or an existing Net::SSLeay object). 1449C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1249 1450
1250The second argument is the optional C<Net::SSLeay::CTX> object that is 1451The second argument is the optional C<AnyEvent::TLS> object that is used
1251used when AnyEvent::Handle has to create its own TLS connection object. 1452when AnyEvent::Handle has to create its own TLS connection object, or
1453a hash reference with C<< key => value >> pairs that will be used to
1454construct a new context.
1252 1455
1253The TLS connection object will end up in C<< $handle->{tls} >> after this 1456The TLS connection object will end up in C<< $handle->{tls} >>, the TLS
1254call and can be used or changed to your liking. Note that the handshake 1457context in C<< $handle->{tls_ctx} >> after this call and can be used or
1255might have already started when this function returns. 1458changed to your liking. Note that the handshake might have already started
1459when this function returns.
1460
1461If it an error to start a TLS handshake more than once per
1462AnyEvent::Handle object (this is due to bugs in OpenSSL).
1256 1463
1257=cut 1464=cut
1258 1465
1259sub starttls { 1466sub starttls {
1260 my ($self, $ssl, $ctx) = @_; 1467 my ($self, $ssl, $ctx) = @_;
1261 1468
1262 $self->stoptls; 1469 require Net::SSLeay;
1263 1470
1264 if ($ssl eq "accept") { 1471 Carp::croak "it is an error to call starttls more than once on an AnyEvent::Handle object"
1265 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1472 if $self->{tls};
1266 Net::SSLeay::set_accept_state ($ssl); 1473
1267 } elsif ($ssl eq "connect") { 1474 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
1268 $ssl = Net::SSLeay::new ($ctx || TLS_CTX ()); 1475 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
1269 Net::SSLeay::set_connect_state ($ssl); 1476 $ERROR_ZERO_RETURN = Net::SSLeay::ERROR_ZERO_RETURN ();
1477
1478 $ctx ||= $self->{tls_ctx};
1479
1480 if ("HASH" eq ref $ctx) {
1481 require AnyEvent::TLS;
1482
1483 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context
1484 $ctx = new AnyEvent::TLS %$ctx;
1485 }
1270 } 1486
1271 1487 $self->{tls_ctx} = $ctx || TLS_CTX ();
1272 $self->{tls} = $ssl; 1488 $self->{tls} = $ssl = $self->{tls_ctx}->_get_session ($ssl, $self, $self->{peername});
1273 1489
1274 # basically, this is deep magic (because SSL_read should have the same issues) 1490 # basically, this is deep magic (because SSL_read should have the same issues)
1275 # but the openssl maintainers basically said: "trust us, it just works". 1491 # but the openssl maintainers basically said: "trust us, it just works".
1276 # (unfortunately, we have to hardcode constants because the abysmally misdesigned 1492 # (unfortunately, we have to hardcode constants because the abysmally misdesigned
1277 # and mismaintained ssleay-module doesn't even offer them). 1493 # and mismaintained ssleay-module doesn't even offer them).
1278 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html 1494 # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html
1495 #
1496 # in short: this is a mess.
1497 #
1498 # note that we do not try to keep the length constant between writes as we are required to do.
1499 # we assume that most (but not all) of this insanity only applies to non-blocking cases,
1500 # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to
1501 # have identity issues in that area.
1279 Net::SSLeay::CTX_set_mode ($self->{tls}, 1502# Net::SSLeay::CTX_set_mode ($ssl,
1280 (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) 1503# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
1281 | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); 1504# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
1505 Net::SSLeay::CTX_set_mode ($ssl, 1|2);
1282 1506
1283 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1507 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1284 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 1508 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1285 1509
1286 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio}); 1510 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio});
1287 1511
1288 $self->{filter_w} = sub { 1512 &_dotls; # need to trigger the initial handshake
1289 $_[0]{_tls_wbuf} .= ${$_[1]}; 1513 $self->start_read; # make sure we actually do read
1290 &_dotls;
1291 };
1292 $self->{filter_r} = sub {
1293 Net::SSLeay::BIO_write ($_[0]{_rbio}, ${$_[1]});
1294 &_dotls;
1295 };
1296} 1514}
1297 1515
1298=item $handle->stoptls 1516=item $handle->stoptls
1299 1517
1300Destroys the SSL connection, if any. Partial read or write data will be 1518Shuts down the SSL connection - this makes a proper EOF handshake by
1301lost. 1519sending a close notify to the other side, but since OpenSSL doesn't
1520support non-blocking shut downs, it is not possible to re-use the stream
1521afterwards.
1302 1522
1303=cut 1523=cut
1304 1524
1305sub stoptls { 1525sub stoptls {
1306 my ($self) = @_; 1526 my ($self) = @_;
1307 1527
1308 Net::SSLeay::free (delete $self->{tls}) if $self->{tls}; 1528 if ($self->{tls}) {
1529 Net::SSLeay::shutdown ($self->{tls});
1309 1530
1310 delete $self->{_rbio}; 1531 &_dotls;
1311 delete $self->{_wbio}; 1532
1312 delete $self->{_tls_wbuf}; 1533 # we don't give a shit. no, we do, but we can't. no...
1313 delete $self->{filter_r}; 1534 # we, we... have to use openssl :/
1314 delete $self->{filter_w}; 1535 &_freetls;
1536 }
1537}
1538
1539sub _freetls {
1540 my ($self) = @_;
1541
1542 return unless $self->{tls};
1543
1544 $self->{tls_ctx}->_put_session (delete $self->{tls});
1545
1546 delete @$self{qw(_rbio _wbio _tls_wbuf)};
1315} 1547}
1316 1548
1317sub DESTROY { 1549sub DESTROY {
1318 my $self = shift; 1550 my ($self) = @_;
1319 1551
1320 $self->stoptls; 1552 &_freetls;
1321 1553
1322 my $linger = exists $self->{linger} ? $self->{linger} : 3600; 1554 my $linger = exists $self->{linger} ? $self->{linger} : 3600;
1323 1555
1324 if ($linger && length $self->{wbuf}) { 1556 if ($linger && length $self->{wbuf}) {
1325 my $fh = delete $self->{fh}; 1557 my $fh = delete $self->{fh};
1340 @linger = (); 1572 @linger = ();
1341 }); 1573 });
1342 } 1574 }
1343} 1575}
1344 1576
1577=item $handle->destroy
1578
1579Shuts down the handle object as much as possible - this call ensures that
1580no further callbacks will be invoked and resources will be freed as much
1581as possible. You must not call any methods on the object afterwards.
1582
1583Normally, you can just "forget" any references to an AnyEvent::Handle
1584object and it will simply shut down. This works in fatal error and EOF
1585callbacks, as well as code outside. It does I<NOT> work in a read or write
1586callback, so when you want to destroy the AnyEvent::Handle object from
1587within such an callback. You I<MUST> call C<< ->destroy >> explicitly in
1588that case.
1589
1590The handle might still linger in the background and write out remaining
1591data, as specified by the C<linger> option, however.
1592
1593=cut
1594
1595sub destroy {
1596 my ($self) = @_;
1597
1598 $self->DESTROY;
1599 %$self = ();
1600}
1601
1345=item AnyEvent::Handle::TLS_CTX 1602=item AnyEvent::Handle::TLS_CTX
1346 1603
1347This function creates and returns the Net::SSLeay::CTX object used by 1604This function creates and returns the AnyEvent::TLS object used by default
1348default for TLS mode. 1605for TLS mode.
1349 1606
1350The context is created like this: 1607The context is created by calling L<AnyEvent::TLS> without any arguments.
1351
1352 Net::SSLeay::load_error_strings;
1353 Net::SSLeay::SSLeay_add_ssl_algorithms;
1354 Net::SSLeay::randomize;
1355
1356 my $CTX = Net::SSLeay::CTX_new;
1357
1358 Net::SSLeay::CTX_set_options $CTX, Net::SSLeay::OP_ALL
1359 1608
1360=cut 1609=cut
1361 1610
1362our $TLS_CTX; 1611our $TLS_CTX;
1363 1612
1364sub TLS_CTX() { 1613sub TLS_CTX() {
1365 $TLS_CTX || do { 1614 $TLS_CTX ||= do {
1366 require Net::SSLeay; 1615 require AnyEvent::TLS;
1367 1616
1368 Net::SSLeay::load_error_strings (); 1617 new AnyEvent::TLS
1369 Net::SSLeay::SSLeay_add_ssl_algorithms ();
1370 Net::SSLeay::randomize ();
1371
1372 $TLS_CTX = Net::SSLeay::CTX_new ();
1373
1374 Net::SSLeay::CTX_set_options ($TLS_CTX, Net::SSLeay::OP_ALL ());
1375
1376 $TLS_CTX
1377 } 1618 }
1378} 1619}
1379 1620
1380=back 1621=back
1622
1623
1624=head1 NONFREQUENTLY ASKED QUESTIONS
1625
1626=over 4
1627
1628=item I C<undef> the AnyEvent::Handle reference inside my callback and
1629still get further invocations!
1630
1631That's because AnyEvent::Handle keeps a reference to itself when handling
1632read or write callbacks.
1633
1634It is only safe to "forget" the reference inside EOF or error callbacks,
1635from within all other callbacks, you need to explicitly call the C<<
1636->destroy >> method.
1637
1638=item I get different callback invocations in TLS mode/Why can't I pause
1639reading?
1640
1641Unlike, say, TCP, TLS connections do not consist of two independent
1642communication channels, one for each direction. Or put differently. The
1643read and write directions are not independent of each other: you cannot
1644write data unless you are also prepared to read, and vice versa.
1645
1646This can mean than, in TLS mode, you might get C<on_error> or C<on_eof>
1647callback invocations when you are not expecting any read data - the reason
1648is that AnyEvent::Handle always reads in TLS mode.
1649
1650During the connection, you have to make sure that you always have a
1651non-empty read-queue, or an C<on_read> watcher. At the end of the
1652connection (or when you no longer want to use it) you can call the
1653C<destroy> method.
1654
1655=item How do I read data until the other side closes the connection?
1656
1657If you just want to read your data into a perl scalar, the easiest way
1658to achieve this is by setting an C<on_read> callback that does nothing,
1659clearing the C<on_eof> callback and in the C<on_error> callback, the data
1660will be in C<$_[0]{rbuf}>:
1661
1662 $handle->on_read (sub { });
1663 $handle->on_eof (undef);
1664 $handle->on_error (sub {
1665 my $data = delete $_[0]{rbuf};
1666 undef $handle;
1667 });
1668
1669The reason to use C<on_error> is that TCP connections, due to latencies
1670and packets loss, might get closed quite violently with an error, when in
1671fact, all data has been received.
1672
1673It is usually better to use acknowledgements when transferring data,
1674to make sure the other side hasn't just died and you got the data
1675intact. This is also one reason why so many internet protocols have an
1676explicit QUIT command.
1677
1678=item I don't want to destroy the handle too early - how do I wait until
1679all data has been written?
1680
1681After writing your last bits of data, set the C<on_drain> callback
1682and destroy the handle in there - with the default setting of
1683C<low_water_mark> this will be called precisely when all data has been
1684written to the socket:
1685
1686 $handle->push_write (...);
1687 $handle->on_drain (sub {
1688 warn "all data submitted to the kernel\n";
1689 undef $handle;
1690 });
1691
1692=back
1693
1381 1694
1382=head1 SUBCLASSING AnyEvent::Handle 1695=head1 SUBCLASSING AnyEvent::Handle
1383 1696
1384In many cases, you might want to subclass AnyEvent::Handle. 1697In many cases, you might want to subclass AnyEvent::Handle.
1385 1698
1389=over 4 1702=over 4
1390 1703
1391=item * all constructor arguments become object members. 1704=item * all constructor arguments become object members.
1392 1705
1393At least initially, when you pass a C<tls>-argument to the constructor it 1706At least initially, when you pass a C<tls>-argument to the constructor it
1394will end up in C<< $handle->{tls} >>. Those members might be changes or 1707will end up in C<< $handle->{tls} >>. Those members might be changed or
1395mutated later on (for example C<tls> will hold the TLS connection object). 1708mutated later on (for example C<tls> will hold the TLS connection object).
1396 1709
1397=item * other object member names are prefixed with an C<_>. 1710=item * other object member names are prefixed with an C<_>.
1398 1711
1399All object members not explicitly documented (internal use) are prefixed 1712All object members not explicitly documented (internal use) are prefixed

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines