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.145 by root, Mon Jul 6 21:47:14 2009 UTC vs.
Revision 1.248 by root, Sun Oct 30 23:03:36 2016 UTC

1package AnyEvent::Handle;
2
3no warnings;
4use strict qw(subs vars);
5
6use AnyEvent ();
7use AnyEvent::Util qw(WSAEWOULDBLOCK);
8use Scalar::Util ();
9use Carp ();
10use Fcntl ();
11use Errno qw(EAGAIN EINTR);
12
13=head1 NAME 1=head1 NAME
14 2
15AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent 3AnyEvent::Handle - non-blocking I/O on streaming handles via AnyEvent
16
17=cut
18
19our $VERSION = 4.8;
20 4
21=head1 SYNOPSIS 5=head1 SYNOPSIS
22 6
23 use AnyEvent; 7 use AnyEvent;
24 use AnyEvent::Handle; 8 use AnyEvent::Handle;
25 9
26 my $cv = AnyEvent->condvar; 10 my $cv = AnyEvent->condvar;
27 11
28 my $handle = 12 my $hdl; $hdl = new AnyEvent::Handle
29 AnyEvent::Handle->new (
30 fh => \*STDIN, 13 fh => \*STDIN,
31 on_eof => sub { 14 on_error => sub {
15 my ($hdl, $fatal, $msg) = @_;
16 AE::log error => $msg;
17 $hdl->destroy;
32 $cv->send; 18 $cv->send;
33 },
34 ); 19 };
35 20
36 # send some request line 21 # send some request line
37 $handle->push_write ("getinfo\015\012"); 22 $hdl->push_write ("getinfo\015\012");
38 23
39 # read the response line 24 # read the response line
40 $handle->push_read (line => sub { 25 $hdl->push_read (line => sub {
41 my ($handle, $line) = @_; 26 my ($hdl, $line) = @_;
42 warn "read line <$line>\n"; 27 say "got line <$line>";
43 $cv->send; 28 $cv->send;
44 }); 29 });
45 30
46 $cv->recv; 31 $cv->recv;
47 32
48=head1 DESCRIPTION 33=head1 DESCRIPTION
49 34
50This module is a helper module to make it easier to do event-based I/O on 35This is a helper module to make it easier to do event-based I/O
51filehandles. For utility functions for doing non-blocking connects and accepts 36on stream-based filehandles (sockets, pipes, and other stream
52on sockets see L<AnyEvent::Util>. 37things). Specifically, it doesn't work as expected on files, packet-based
38sockets or similar things.
53 39
54The L<AnyEvent::Intro> tutorial contains some well-documented 40The L<AnyEvent::Intro> tutorial contains some well-documented
55AnyEvent::Handle examples. 41AnyEvent::Handle examples.
56 42
57In the following, when the documentation refers to of "bytes" then this 43In the following, where the documentation refers to "bytes", it means
58means characters. As sysread and syswrite are used for all I/O, their 44characters. As sysread and syswrite are used for all I/O, their
59treatment of characters applies to this module as well. 45treatment of characters applies to this module as well.
46
47At the very minimum, you should specify C<fh> or C<connect>, and the
48C<on_error> callback.
60 49
61All callbacks will be invoked with the handle object as their first 50All callbacks will be invoked with the handle object as their first
62argument. 51argument.
63 52
53=cut
54
55package AnyEvent::Handle;
56
57use Scalar::Util ();
58use List::Util ();
59use Carp ();
60use Errno qw(EAGAIN EWOULDBLOCK EINTR);
61
62use AnyEvent (); BEGIN { AnyEvent::common_sense }
63use AnyEvent::Util qw(WSAEWOULDBLOCK);
64
65our $VERSION = $AnyEvent::VERSION;
66
67sub _load_func($) {
68 my $func = $_[0];
69
70 unless (defined &$func) {
71 my $pkg = $func;
72 do {
73 $pkg =~ s/::[^:]+$//
74 or return;
75 eval "require $pkg";
76 } until defined &$func;
77 }
78
79 \&$func
80}
81
82sub MAX_READ_SIZE() { 131072 }
83
64=head1 METHODS 84=head1 METHODS
65 85
66=over 4 86=over 4
67 87
68=item $handle = B<new> AnyEvent::TLS fh => $filehandle, key => value... 88=item $handle = B<new> AnyEvent::Handle fh => $filehandle, key => value...
69 89
70The constructor supports these arguments (all as C<< key => value >> pairs). 90The constructor supports these arguments (all as C<< key => value >> pairs).
71 91
72=over 4 92=over 4
73 93
74=item fh => $filehandle [MANDATORY] 94=item fh => $filehandle [C<fh> or C<connect> MANDATORY]
75 95
76The filehandle this L<AnyEvent::Handle> object will operate on. 96The filehandle this L<AnyEvent::Handle> object will operate on.
77
78NOTE: The filehandle will be set to non-blocking mode (using 97NOTE: The filehandle will be set to non-blocking mode (using
79C<AnyEvent::Util::fh_nonblocking>) by the constructor and needs to stay in 98C<AnyEvent::fh_unblock>) by the constructor and needs to stay in
80that mode. 99that mode.
100
101=item connect => [$host, $service] [C<fh> or C<connect> MANDATORY]
102
103Try to connect to the specified host and service (port), using
104C<AnyEvent::Socket::tcp_connect>. The C<$host> additionally becomes the
105default C<peername>.
106
107You have to specify either this parameter, or C<fh>, above.
108
109It is possible to push requests on the read and write queues, and modify
110properties of the stream, even while AnyEvent::Handle is connecting.
111
112When this parameter is specified, then the C<on_prepare>,
113C<on_connect_error> and C<on_connect> callbacks will be called under the
114appropriate circumstances:
115
116=over 4
117
118=item on_prepare => $cb->($handle)
119
120This (rarely used) callback is called before a new connection is
121attempted, but after the file handle has been created (you can access that
122file handle via C<< $handle->{fh} >>). It could be used to prepare the
123file handle with parameters required for the actual connect (as opposed to
124settings that can be changed when the connection is already established).
125
126The return value of this callback should be the connect timeout value in
127seconds (or C<0>, or C<undef>, or the empty list, to indicate that the
128default timeout is to be used).
129
130=item on_connect => $cb->($handle, $host, $port, $retry->())
131
132This callback is called when a connection has been successfully established.
133
134The peer's numeric host and port (the socket peername) are passed as
135parameters, together with a retry callback. At the time it is called the
136read and write queues, EOF status, TLS status and similar properties of
137the handle will have been reset.
138
139If, for some reason, the handle is not acceptable, calling C<$retry> will
140continue with the next connection target (in case of multi-homed hosts or
141SRV records there can be multiple connection endpoints). The C<$retry>
142callback can be invoked after the connect callback returns, i.e. one can
143start a handshake and then decide to retry with the next host if the
144handshake fails.
145
146In most cases, you should ignore the C<$retry> parameter.
147
148=item on_connect_error => $cb->($handle, $message)
149
150This callback is called when the connection could not be
151established. C<$!> will contain the relevant error code, and C<$message> a
152message describing it (usually the same as C<"$!">).
153
154If this callback isn't specified, then C<on_error> will be called with a
155fatal error instead.
156
157=back
158
159=item on_error => $cb->($handle, $fatal, $message)
160
161This is the error callback, which is called when, well, some error
162occured, such as not being able to resolve the hostname, failure to
163connect, or a read error.
164
165Some errors are fatal (which is indicated by C<$fatal> being true). On
166fatal errors the handle object will be destroyed (by a call to C<< ->
167destroy >>) after invoking the error callback (which means you are free to
168examine the handle object). Examples of fatal errors are an EOF condition
169with active (but unsatisfiable) read watchers (C<EPIPE>) or I/O errors. In
170cases where the other side can close the connection at will, it is
171often easiest to not report C<EPIPE> errors in this callback.
172
173AnyEvent::Handle tries to find an appropriate error code for you to check
174against, but in some cases (TLS errors), this does not work well.
175
176If you report the error to the user, it is recommended to always output
177the C<$message> argument in human-readable error messages (you don't need
178to report C<"$!"> if you report C<$message>).
179
180If you want to react programmatically to the error, then looking at C<$!>
181and comparing it against some of the documented C<Errno> values is usually
182better than looking at the C<$message>.
183
184Non-fatal errors can be retried by returning, but it is recommended
185to simply ignore this parameter and instead abondon the handle object
186when this callback is invoked. Examples of non-fatal errors are timeouts
187C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
188
189On entry to the callback, the value of C<$!> contains the operating
190system error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
191C<EPROTO>).
192
193While not mandatory, it is I<highly> recommended to set this callback, as
194you will not be notified of errors otherwise. The default just calls
195C<croak>.
196
197=item on_read => $cb->($handle)
198
199This sets the default read callback, which is called when data arrives
200and no read request is in the queue (unlike read queue callbacks, this
201callback will only be called when at least one octet of data is in the
202read buffer).
203
204To access (and remove data from) the read buffer, use the C<< ->rbuf >>
205method or access the C<< $handle->{rbuf} >> member directly. Note that you
206must not enlarge or modify the read buffer, you can only remove data at
207the beginning from it.
208
209You can also call C<< ->push_read (...) >> or any other function that
210modifies the read queue. Or do both. Or ...
211
212When an EOF condition is detected, AnyEvent::Handle will first try to
213feed all the remaining data to the queued callbacks and C<on_read> before
214calling the C<on_eof> callback. If no progress can be made, then a fatal
215error will be raised (with C<$!> set to C<EPIPE>).
216
217Note that, unlike requests in the read queue, an C<on_read> callback
218doesn't mean you I<require> some data: if there is an EOF and there
219are outstanding read requests then an error will be flagged. With an
220C<on_read> callback, the C<on_eof> callback will be invoked.
81 221
82=item on_eof => $cb->($handle) 222=item on_eof => $cb->($handle)
83 223
84Set the callback to be called when an end-of-file condition is detected, 224Set the callback to be called when an end-of-file condition is detected,
85i.e. in the case of a socket, when the other side has closed the 225i.e. in the case of a socket, when the other side has closed the
86connection cleanly. 226connection cleanly, and there are no outstanding read requests in the
227queue (if there are read requests, then an EOF counts as an unexpected
228connection close and will be flagged as an error).
87 229
88For sockets, this just means that the other side has stopped sending data, 230For 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 231you 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 232callback and continue writing data, as only the read part has been shut
91down. 233down.
92 234
93While not mandatory, it is I<highly> recommended to set an EOF callback,
94otherwise you might end up with a closed socket while you are still
95waiting for data.
96
97If an EOF condition has been detected but no C<on_eof> callback has been 235If 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>. 236set, then a fatal error will be raised with C<$!> set to <0>.
99 237
100=item on_error => $cb->($handle, $fatal, $message)
101
102This is the error callback, which is called when, well, some error
103occured, such as not being able to resolve the hostname, failure to
104connect or a read error.
105
106Some errors are fatal (which is indicated by C<$fatal> being true). On
107fatal errors the handle object will be shut down and will not be usable
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
117Non-fatal errors can be retried by simply returning, but it is recommended
118to simply ignore this parameter and instead abondon the handle object
119when this callback is invoked. Examples of non-fatal errors are timeouts
120C<ETIMEDOUT>) or badly-formatted data (C<EBADMSG>).
121
122On callback entrance, the value of C<$!> contains the operating system
123error code (or C<ENOSPC>, C<EPIPE>, C<ETIMEDOUT>, C<EBADMSG> or
124C<EPROTO>).
125
126While not mandatory, it is I<highly> recommended to set this callback, as
127you will not be notified of errors otherwise. The default simply calls
128C<croak>.
129
130=item on_read => $cb->($handle)
131
132This sets the default read callback, which is called when data arrives
133and no read request is in the queue (unlike read queue callbacks, this
134callback will only be called when at least one octet of data is in the
135read buffer).
136
137To access (and remove data from) the read buffer, use the C<< ->rbuf >>
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.
141
142When an EOF condition is detected then AnyEvent::Handle will first try to
143feed all the remaining data to the queued callbacks and C<on_read> before
144calling the C<on_eof> callback. If no progress can be made, then a fatal
145error will be raised (with C<$!> set to C<EPIPE>).
146
147=item on_drain => $cb->($handle) 238=item on_drain => $cb->($handle)
148 239
149This sets the callback that is called when the write buffer becomes empty 240This sets the callback that is called once when the write buffer becomes
150(or when the callback is set and the buffer is empty already). 241empty (and immediately when the handle object is created).
151 242
152To append to the write buffer, use the C<< ->push_write >> method. 243To append to the write buffer, use the C<< ->push_write >> method.
153 244
154This callback is useful when you don't want to put all of your write data 245This 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 246into the queue at once, for example, when you want to write the contents
157memory and push it into the queue, but instead only read more data from 248memory and push it into the queue, but instead only read more data from
158the file when the write queue becomes empty. 249the file when the write queue becomes empty.
159 250
160=item timeout => $fractional_seconds 251=item timeout => $fractional_seconds
161 252
253=item rtimeout => $fractional_seconds
254
255=item wtimeout => $fractional_seconds
256
162If non-zero, then this enables an "inactivity" timeout: whenever this many 257If non-zero, then these enables an "inactivity" timeout: whenever this
163seconds pass without a successful read or write on the underlying file 258many seconds pass without a successful read or write on the underlying
164handle, the C<on_timeout> callback will be invoked (and if that one is 259file handle (or a call to C<timeout_reset>), the C<on_timeout> callback
165missing, a non-fatal C<ETIMEDOUT> error will be raised). 260will be invoked (and if that one is missing, a non-fatal C<ETIMEDOUT>
261error will be raised).
166 262
263There are three variants of the timeouts that work independently of each
264other, for both read and write (triggered when nothing was read I<OR>
265written), just read (triggered when nothing was read), and just write:
266C<timeout>, C<rtimeout> and C<wtimeout>, with corresponding callbacks
267C<on_timeout>, C<on_rtimeout> and C<on_wtimeout>, and reset functions
268C<timeout_reset>, C<rtimeout_reset>, and C<wtimeout_reset>.
269
167Note that timeout processing is also active when you currently do not have 270Note that timeout processing is active even when you do not have any
168any outstanding read or write requests: If you plan to keep the connection 271outstanding read or write requests: If you plan to keep the connection
169idle then you should disable the timout temporarily or ignore the timeout 272idle then you should disable the timeout temporarily or ignore the
170in the C<on_timeout> callback, in which case AnyEvent::Handle will simply 273timeout in the corresponding C<on_timeout> callback, in which case
171restart the timeout. 274AnyEvent::Handle will simply restart the timeout.
172 275
173Zero (the default) disables this timeout. 276Zero (the default) disables the corresponding timeout.
174 277
175=item on_timeout => $cb->($handle) 278=item on_timeout => $cb->($handle)
279
280=item on_rtimeout => $cb->($handle)
281
282=item on_wtimeout => $cb->($handle)
176 283
177Called whenever the inactivity timeout passes. If you return from this 284Called whenever the inactivity timeout passes. If you return from this
178callback, then the timeout will be reset as if some activity had happened, 285callback, then the timeout will be reset as if some activity had happened,
179so this condition is not fatal in any way. 286so this condition is not fatal in any way.
180 287
188be configured to accept only so-and-so much data that it cannot act on 295be configured to accept only so-and-so much data that it cannot act on
189(for example, when expecting a line, an attacker could send an unlimited 296(for example, when expecting a line, an attacker could send an unlimited
190amount of data without a callback ever being called as long as the line 297amount of data without a callback ever being called as long as the line
191isn't finished). 298isn't finished).
192 299
300=item wbuf_max => <bytes>
301
302If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>)
303when the write buffer ever (strictly) exceeds this size. This is useful to
304avoid some forms of denial-of-service attacks.
305
306Although the units of this parameter is bytes, this is the I<raw> number
307of bytes not yet accepted by the kernel. This can make a difference when
308you e.g. use TLS, as TLS typically makes your write data larger (but it
309can also make it smaller due to compression).
310
311As an example of when this limit is useful, take a chat server that sends
312chat messages to a client. If the client does not read those in a timely
313manner then the send buffer in the server would grow unbounded.
314
193=item autocork => <boolean> 315=item autocork => <boolean>
194 316
195When disabled (the default), then C<push_write> will try to immediately 317When disabled (the default), C<push_write> will try to immediately
196write the data to the handle, if possible. This avoids having to register 318write 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 319a write watcher and wait for the next event loop iteration, but can
198be inefficient if you write multiple small chunks (on the wire, this 320be inefficient if you write multiple small chunks (on the wire, this
199disadvantage is usually avoided by your kernel's nagle algorithm, see 321disadvantage is usually avoided by your kernel's nagle algorithm, see
200C<no_delay>, but this option can save costly syscalls). 322C<no_delay>, but this option can save costly syscalls).
201 323
202When enabled, then writes will always be queued till the next event loop 324When enabled, writes will always be queued till the next event loop
203iteration. This is efficient when you do many small writes per iteration, 325iteration. 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 326but less efficient when you do a single write only per iteration (or when
205the write buffer often is full). It also increases write latency. 327the write buffer often is full). It also increases write latency.
206 328
207=item no_delay => <boolean> 329=item no_delay => <boolean>
211the Nagle algorithm, and usually it is beneficial. 333the Nagle algorithm, and usually it is beneficial.
212 334
213In some situations you want as low a delay as possible, which can be 335In some situations you want as low a delay as possible, which can be
214accomplishd by setting this option to a true value. 336accomplishd by setting this option to a true value.
215 337
216The default is your opertaing system's default behaviour (most likely 338The default is your operating system's default behaviour (most likely
217enabled), this option explicitly enables or disables it, if possible. 339enabled). This option explicitly enables or disables it, if possible.
340
341=item keepalive => <boolean>
342
343Enables (default disable) the SO_KEEPALIVE option on the stream socket:
344normally, TCP connections have no time-out once established, so TCP
345connections, once established, can stay alive forever even when the other
346side has long gone. TCP keepalives are a cheap way to take down long-lived
347TCP connections when the other side becomes unreachable. While the default
348is OS-dependent, TCP keepalives usually kick in after around two hours,
349and, if the other side doesn't reply, take down the TCP connection some 10
350to 15 minutes later.
351
352It is harmless to specify this option for file handles that do not support
353keepalives, and enabling it on connections that are potentially long-lived
354is usually a good idea.
355
356=item oobinline => <boolean>
357
358BSD majorly fucked up the implementation of TCP urgent data. The result
359is that almost no OS implements TCP according to the specs, and every OS
360implements it slightly differently.
361
362If you want to handle TCP urgent data, then setting this flag (the default
363is enabled) gives you the most portable way of getting urgent data, by
364putting it into the stream.
365
366Since BSD emulation of OOB data on top of TCP's urgent data can have
367security implications, AnyEvent::Handle sets this flag automatically
368unless explicitly specified. Note that setting this flag after
369establishing a connection I<may> be a bit too late (data loss could
370already have occured on BSD systems), but at least it will protect you
371from most attacks.
218 372
219=item read_size => <bytes> 373=item read_size => <bytes>
220 374
221The default read block size (the amount of bytes this module will 375The initial read block size, the number of bytes this module will try
222try to read during each loop iteration, which affects memory 376to read during each loop iteration. Each handle object will consume
223requirements). Default: C<8192>. 377at least this amount of memory for the read buffer as well, so when
378handling many connections watch out for memory requirements). See also
379C<max_read_size>. Default: C<2048>.
380
381=item max_read_size => <bytes>
382
383The maximum read buffer size used by the dynamic adjustment
384algorithm: Each time AnyEvent::Handle can read C<read_size> bytes in
385one go it will double C<read_size> up to the maximum given by this
386option. Default: C<131072> or C<read_size>, whichever is higher.
224 387
225=item low_water_mark => <bytes> 388=item low_water_mark => <bytes>
226 389
227Sets the amount of bytes (default: C<0>) that make up an "empty" write 390Sets the number of bytes (default: C<0>) that make up an "empty" write
228buffer: If the write reaches this size or gets even samller it is 391buffer: If the buffer reaches this size or gets even samller it is
229considered empty. 392considered empty.
230 393
231Sometimes it can be beneficial (for performance reasons) to add data to 394Sometimes 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 395the 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 396the operating system kernel usually buffers data as well, so the default
234is good in almost all cases. 397is good in almost all cases.
235 398
236=item linger => <seconds> 399=item linger => <seconds>
237 400
238If non-zero (default: C<3600>), then the destructor of the 401If this is non-zero (default: C<3600>), the destructor of the
239AnyEvent::Handle object will check whether there is still outstanding 402AnyEvent::Handle object will check whether there is still outstanding
240write data and will install a watcher that will write this data to the 403write data and will install a watcher that will write this data to the
241socket. No errors will be reported (this mostly matches how the operating 404socket. No errors will be reported (this mostly matches how the operating
242system treats outstanding data at socket close time). 405system treats outstanding data at socket close time).
243 406
250A string used to identify the remote site - usually the DNS hostname 413A string used to identify the remote site - usually the DNS hostname
251(I<not> IDN!) used to create the connection, rarely the IP address. 414(I<not> IDN!) used to create the connection, rarely the IP address.
252 415
253Apart from being useful in error messages, this string is also used in TLS 416Apart from being useful in error messages, this string is also used in TLS
254peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This 417peername verification (see C<verify_peername> in L<AnyEvent::TLS>). This
255verification will be skipped when C<peername> is not specified or 418verification will be skipped when C<peername> is not specified or is
256C<undef>. 419C<undef>.
257 420
258=item tls => "accept" | "connect" | Net::SSLeay::SSL object 421=item tls => "accept" | "connect" | Net::SSLeay::SSL object
259 422
260When this parameter is given, it enables TLS (SSL) mode, that means 423When this parameter is given, it enables TLS (SSL) mode, that means
261AnyEvent will start a TLS handshake as soon as the conenction has been 424AnyEvent will start a TLS handshake as soon as the connection has been
262established and will transparently encrypt/decrypt data afterwards. 425established and will transparently encrypt/decrypt data afterwards.
263 426
264All TLS protocol errors will be signalled as C<EPROTO>, with an 427All TLS protocol errors will be signalled as C<EPROTO>, with an
265appropriate error message. 428appropriate error message.
266 429
267TLS mode requires Net::SSLeay to be installed (it will be loaded 430TLS mode requires Net::SSLeay to be installed (it will be loaded
268automatically when you try to create a TLS handle): this module doesn't 431automatically when you try to create a TLS handle): this module doesn't
269have a dependency on that module, so if your module requires it, you have 432have a dependency on that module, so if your module requires it, you have
270to add the dependency yourself. 433to add the dependency yourself. If Net::SSLeay cannot be loaded or is too
434old, you get an C<EPROTO> error.
271 435
272Unlike TCP, TLS has a server and client side: for the TLS server side, use 436Unlike TCP, TLS has a server and client side: for the TLS server side, use
273C<accept>, and for the TLS client side of a connection, use C<connect> 437C<accept>, and for the TLS client side of a connection, use C<connect>
274mode. 438mode.
275 439
286B<IMPORTANT:> since Net::SSLeay "objects" are really only integers, 450B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
287passing in the wrong integer will lead to certain crash. This most often 451passing in the wrong integer will lead to certain crash. This most often
288happens when one uses a stylish C<< tls => 1 >> and is surprised about the 452happens when one uses a stylish C<< tls => 1 >> and is surprised about the
289segmentation fault. 453segmentation fault.
290 454
291See the C<< ->starttls >> method for when need to start TLS negotiation later. 455Use the C<< ->starttls >> method if you need to start TLS negotiation later.
292 456
293=item tls_ctx => $anyevent_tls 457=item tls_ctx => $anyevent_tls
294 458
295Use the given C<AnyEvent::TLS> object to create the new TLS connection 459Use the given C<AnyEvent::TLS> object to create the new TLS connection
296(unless a connection object was specified directly). If this parameter is 460(unless a connection object was specified directly). If this
297missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>. 461parameter is missing (or C<undef>), then AnyEvent::Handle will use
462C<AnyEvent::Handle::TLS_CTX>.
298 463
299Instead of an object, you can also specify a hash reference with C<< key 464Instead of an object, you can also specify a hash reference with C<< key
300=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a 465=> value >> pairs. Those will be passed to L<AnyEvent::TLS> to create a
301new TLS context object. 466new TLS context object.
302 467
311 476
312TLS handshake failures will not cause C<on_error> to be invoked when this 477TLS handshake failures will not cause C<on_error> to be invoked when this
313callback is in effect, instead, the error message will be passed to C<on_starttls>. 478callback is in effect, instead, the error message will be passed to C<on_starttls>.
314 479
315Without this callback, handshake failures lead to C<on_error> being 480Without this callback, handshake failures lead to C<on_error> being
316called, as normal. 481called as usual.
317 482
318Note that you cannot call C<starttls> right again in this callback. If you 483Note that you cannot just call C<starttls> again in this callback. If you
319need to do that, start an zero-second timer instead whose callback can 484need to do that, start an zero-second timer instead whose callback can
320then call C<< ->starttls >> again. 485then call C<< ->starttls >> again.
321 486
322=item on_stoptls => $cb->($handle) 487=item on_stoptls => $cb->($handle)
323 488
330callback. 495callback.
331 496
332This callback will only be called on TLS shutdowns, not when the 497This callback will only be called on TLS shutdowns, not when the
333underlying handle signals EOF. 498underlying handle signals EOF.
334 499
335=item json => JSON or JSON::XS object 500=item json => L<JSON>, L<JSON::PP> or L<JSON::XS> object
336 501
337This is the json coder object used by the C<json> read and write types. 502This is the json coder object used by the C<json> read and write types.
338 503
339If you don't supply it, then AnyEvent::Handle will create and use a 504If you don't supply it, then AnyEvent::Handle will create and use a
340suitable one (on demand), which will write and expect UTF-8 encoded JSON 505suitable one (on demand), which will write and expect UTF-8 encoded
506JSON texts (either using L<JSON::XS> or L<JSON>). The written texts are
507guaranteed not to contain any newline character.
508
509For security reasons, this encoder will likely I<not> handle numbers and
510strings, only arrays and objects/hashes. The reason is that originally
511JSON was self-delimited, but Dougles Crockford thought it was a splendid
512idea to redefine JSON incompatibly, so this is no longer true.
513
514For protocols that used back-to-back JSON texts, this might lead to
515run-ins, where two or more JSON texts will be interpreted as one JSON
341texts. 516text.
342 517
518For this reason, if the default encoder uses L<JSON::XS>, it will default
519to not allowing anything but arrays and objects/hashes, at least for the
520forseeable future (it will change at some point). This might or might not
521be true for the L<JSON> module, so this might cause a security issue.
522
523If you depend on either behaviour, you should create your own json object
524and pass it in explicitly.
525
526=item cbor => L<CBOR::XS> object
527
528This is the cbor coder object used by the C<cbor> read and write types.
529
530If you don't supply it, then AnyEvent::Handle will create and use a
531suitable one (on demand), which will write CBOR without using extensions,
532if possible.
533
343Note that you are responsible to depend on the JSON module if you want to 534Note that you are responsible to depend on the L<CBOR::XS> module if you
344use this functionality, as AnyEvent does not have a dependency itself. 535want to use this functionality, as AnyEvent does not have a dependency on
536it itself.
345 537
346=back 538=back
347 539
348=cut 540=cut
349 541
350sub new { 542sub new {
351 my $class = shift; 543 my $class = shift;
352 my $self = bless { @_ }, $class; 544 my $self = bless { @_ }, $class;
353 545
354 $self->{fh} or Carp::croak "mandatory argument fh is missing"; 546 if ($self->{fh}) {
547 $self->_start;
548 return unless $self->{fh}; # could be gone by now
355 549
550 } elsif ($self->{connect}) {
551 require AnyEvent::Socket;
552
553 $self->{peername} = $self->{connect}[0]
554 unless exists $self->{peername};
555
556 $self->{_skip_drain_rbuf} = 1;
557
558 {
559 Scalar::Util::weaken (my $self = $self);
560
561 $self->{_connect} =
562 AnyEvent::Socket::tcp_connect (
563 $self->{connect}[0],
564 $self->{connect}[1],
565 sub {
566 my ($fh, $host, $port, $retry) = @_;
567
568 delete $self->{_connect}; # no longer needed
569
570 if ($fh) {
571 $self->{fh} = $fh;
572
573 delete $self->{_skip_drain_rbuf};
574 $self->_start;
575
576 $self->{on_connect}
577 and $self->{on_connect}($self, $host, $port, sub {
578 delete @$self{qw(fh _tw _rtw _wtw _ww _rw _eof _queue rbuf _wbuf tls _tls_rbuf _tls_wbuf)};
579 $self->{_skip_drain_rbuf} = 1;
580 &$retry;
581 });
582
583 } else {
584 if ($self->{on_connect_error}) {
585 $self->{on_connect_error}($self, "$!");
586 $self->destroy if $self;
587 } else {
588 $self->_error ($!, 1);
589 }
590 }
591 },
592 sub {
593 local $self->{fh} = $_[0];
594
595 $self->{on_prepare}
596 ? $self->{on_prepare}->($self)
597 : ()
598 }
599 );
600 }
601
602 } else {
603 Carp::croak "AnyEvent::Handle: either an existing fh or the connect parameter must be specified";
604 }
605
606 $self
607}
608
609sub _start {
610 my ($self) = @_;
611
612 # too many clueless people try to use udp and similar sockets
613 # with AnyEvent::Handle, do them a favour.
614 my $type = getsockopt $self->{fh}, Socket::SOL_SOCKET (), Socket::SO_TYPE ();
615 Carp::croak "AnyEvent::Handle: only stream sockets supported, anything else will NOT work!"
616 if Socket::SOCK_STREAM () != (unpack "I", $type) && defined $type;
617
356 AnyEvent::Util::fh_nonblocking $self->{fh}, 1; 618 AnyEvent::fh_unblock $self->{fh};
357 619
620 $self->{_activity} =
621 $self->{_ractivity} =
358 $self->{_activity} = AnyEvent->now; 622 $self->{_wactivity} = AE::now;
359 $self->_timeout;
360 623
624 $self->{read_size} ||= 2048;
625 $self->{max_read_size} = $self->{read_size}
626 if $self->{read_size} > ($self->{max_read_size} || MAX_READ_SIZE);
627
628 $self->timeout (delete $self->{timeout} ) if $self->{timeout};
629 $self->rtimeout (delete $self->{rtimeout} ) if $self->{rtimeout};
630 $self->wtimeout (delete $self->{wtimeout} ) if $self->{wtimeout};
631
361 $self->no_delay (delete $self->{no_delay}) if exists $self->{no_delay}; 632 $self->no_delay (delete $self->{no_delay} ) if exists $self->{no_delay} && $self->{no_delay};
633 $self->keepalive (delete $self->{keepalive}) if exists $self->{keepalive} && $self->{keepalive};
362 634
635 $self->oobinline (exists $self->{oobinline} ? delete $self->{oobinline} : 1);
636
363 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx}) 637 $self->starttls (delete $self->{tls}, delete $self->{tls_ctx})
364 if $self->{tls}; 638 if $self->{tls};
365 639
366 $self->on_drain (delete $self->{on_drain}) if $self->{on_drain}; 640 $self->on_drain (delete $self->{on_drain} ) if $self->{on_drain};
367 641
368 $self->start_read 642 $self->start_read
369 if $self->{on_read}; 643 if $self->{on_read} || @{ $self->{_queue} };
370 644
371 $self->{fh} && $self 645 $self->_drain_wbuf;
372}
373
374sub _shutdown {
375 my ($self) = @_;
376
377 delete @$self{qw(_tw _rw _ww fh wbuf on_read _queue)};
378 $self->{_eof} = 1; # tell starttls et. al to stop trying
379
380 &_freetls;
381} 646}
382 647
383sub _error { 648sub _error {
384 my ($self, $errno, $fatal, $message) = @_; 649 my ($self, $errno, $fatal, $message) = @_;
385 650
386 $self->_shutdown
387 if $fatal;
388
389 $! = $errno; 651 $! = $errno;
390 $message ||= "$!"; 652 $message ||= "$!";
391 653
392 if ($self->{on_error}) { 654 if ($self->{on_error}) {
393 $self->{on_error}($self, $fatal, $message); 655 $self->{on_error}($self, $fatal, $message);
394 } elsif ($self->{fh}) { 656 $self->destroy if $fatal;
657 } elsif ($self->{fh} || $self->{connect}) {
658 $self->destroy;
395 Carp::croak "AnyEvent::Handle uncaught error: $message"; 659 Carp::croak "AnyEvent::Handle uncaught error: $message";
396 } 660 }
397} 661}
398 662
399=item $fh = $handle->fh 663=item $fh = $handle->fh
424 $_[0]{on_eof} = $_[1]; 688 $_[0]{on_eof} = $_[1];
425} 689}
426 690
427=item $handle->on_timeout ($cb) 691=item $handle->on_timeout ($cb)
428 692
429Replace the current C<on_timeout> callback, or disables the callback (but 693=item $handle->on_rtimeout ($cb)
430not the timeout) if C<$cb> = C<undef>. See the C<timeout> constructor
431argument and method.
432 694
433=cut 695=item $handle->on_wtimeout ($cb)
434 696
435sub on_timeout { 697Replace the current C<on_timeout>, C<on_rtimeout> or C<on_wtimeout>
436 $_[0]{on_timeout} = $_[1]; 698callback, or disables the callback (but not the timeout) if C<$cb> =
437} 699C<undef>. See the C<timeout> constructor argument and method.
700
701=cut
702
703# see below
438 704
439=item $handle->autocork ($boolean) 705=item $handle->autocork ($boolean)
440 706
441Enables or disables the current autocork behaviour (see C<autocork> 707Enables or disables the current autocork behaviour (see C<autocork>
442constructor argument). Changes will only take effect on the next write. 708constructor argument). Changes will only take effect on the next write.
455=cut 721=cut
456 722
457sub no_delay { 723sub no_delay {
458 $_[0]{no_delay} = $_[1]; 724 $_[0]{no_delay} = $_[1];
459 725
726 setsockopt $_[0]{fh}, Socket::IPPROTO_TCP (), Socket::TCP_NODELAY (), int $_[1]
727 if $_[0]{fh};
728}
729
730=item $handle->keepalive ($boolean)
731
732Enables or disables the C<keepalive> setting (see constructor argument of
733the same name for details).
734
735=cut
736
737sub keepalive {
738 $_[0]{keepalive} = $_[1];
739
460 eval { 740 eval {
461 local $SIG{__DIE__}; 741 local $SIG{__DIE__};
462 setsockopt $_[0]{fh}, &Socket::IPPROTO_TCP, &Socket::TCP_NODELAY, int $_[1]; 742 setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_KEEPALIVE (), int $_[1]
743 if $_[0]{fh};
744 };
745}
746
747=item $handle->oobinline ($boolean)
748
749Enables or disables the C<oobinline> setting (see constructor argument of
750the same name for details).
751
752=cut
753
754sub oobinline {
755 $_[0]{oobinline} = $_[1];
756
757 eval {
758 local $SIG{__DIE__};
759 setsockopt $_[0]{fh}, Socket::SOL_SOCKET (), Socket::SO_OOBINLINE (), int $_[1]
760 if $_[0]{fh};
463 }; 761 };
464} 762}
465 763
466=item $handle->on_starttls ($cb) 764=item $handle->on_starttls ($cb)
467 765
477 775
478Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument). 776Replace the current C<on_stoptls> callback (see the C<on_stoptls> constructor argument).
479 777
480=cut 778=cut
481 779
482sub on_starttls { 780sub on_stoptls {
483 $_[0]{on_stoptls} = $_[1]; 781 $_[0]{on_stoptls} = $_[1];
484} 782}
485 783
784=item $handle->rbuf_max ($max_octets)
785
786Configures the C<rbuf_max> setting (C<undef> disables it).
787
788=item $handle->wbuf_max ($max_octets)
789
790Configures the C<wbuf_max> setting (C<undef> disables it).
791
792=cut
793
794sub rbuf_max {
795 $_[0]{rbuf_max} = $_[1];
796}
797
798sub wbuf_max {
799 $_[0]{wbuf_max} = $_[1];
800}
801
486############################################################################# 802#############################################################################
487 803
488=item $handle->timeout ($seconds) 804=item $handle->timeout ($seconds)
489 805
806=item $handle->rtimeout ($seconds)
807
808=item $handle->wtimeout ($seconds)
809
490Configures (or disables) the inactivity timeout. 810Configures (or disables) the inactivity timeout.
491 811
492=cut 812The timeout will be checked instantly, so this method might destroy the
813handle before it returns.
493 814
494sub timeout { 815=item $handle->timeout_reset
816
817=item $handle->rtimeout_reset
818
819=item $handle->wtimeout_reset
820
821Reset the activity timeout, as if data was received or sent.
822
823These methods are cheap to call.
824
825=cut
826
827for my $dir ("", "r", "w") {
828 my $timeout = "${dir}timeout";
829 my $tw = "_${dir}tw";
830 my $on_timeout = "on_${dir}timeout";
831 my $activity = "_${dir}activity";
832 my $cb;
833
834 *$on_timeout = sub {
835 $_[0]{$on_timeout} = $_[1];
836 };
837
838 *$timeout = sub {
495 my ($self, $timeout) = @_; 839 my ($self, $new_value) = @_;
496 840
841 $new_value >= 0
842 or Carp::croak "AnyEvent::Handle->$timeout called with negative timeout ($new_value), caught";
843
497 $self->{timeout} = $timeout; 844 $self->{$timeout} = $new_value;
498 $self->_timeout; 845 delete $self->{$tw}; &$cb;
499} 846 };
500 847
848 *{"${dir}timeout_reset"} = sub {
849 $_[0]{$activity} = AE::now;
850 };
851
852 # main workhorse:
501# reset the timeout watcher, as neccessary 853 # reset the timeout watcher, as neccessary
502# also check for time-outs 854 # also check for time-outs
503sub _timeout { 855 $cb = sub {
504 my ($self) = @_; 856 my ($self) = @_;
505 857
506 if ($self->{timeout}) { 858 if ($self->{$timeout} && $self->{fh}) {
507 my $NOW = AnyEvent->now; 859 my $NOW = AE::now;
508 860
509 # when would the timeout trigger? 861 # when would the timeout trigger?
510 my $after = $self->{_activity} + $self->{timeout} - $NOW; 862 my $after = $self->{$activity} + $self->{$timeout} - $NOW;
511 863
512 # now or in the past already? 864 # now or in the past already?
513 if ($after <= 0) { 865 if ($after <= 0) {
514 $self->{_activity} = $NOW; 866 $self->{$activity} = $NOW;
515 867
516 if ($self->{on_timeout}) { 868 if ($self->{$on_timeout}) {
517 $self->{on_timeout}($self); 869 $self->{$on_timeout}($self);
518 } else { 870 } else {
519 $self->_error (&Errno::ETIMEDOUT); 871 $self->_error (Errno::ETIMEDOUT);
872 }
873
874 # callback could have changed timeout value, optimise
875 return unless $self->{$timeout};
876
877 # calculate new after
878 $after = $self->{$timeout};
520 } 879 }
521 880
522 # callback could have changed timeout value, optimise 881 Scalar::Util::weaken $self;
523 return unless $self->{timeout}; 882 return unless $self; # ->error could have destroyed $self
524 883
525 # calculate new after 884 $self->{$tw} ||= AE::timer $after, 0, sub {
526 $after = $self->{timeout}; 885 delete $self->{$tw};
886 $cb->($self);
887 };
888 } else {
889 delete $self->{$tw};
527 } 890 }
528
529 Scalar::Util::weaken $self;
530 return unless $self; # ->error could have destroyed $self
531
532 $self->{_tw} ||= AnyEvent->timer (after => $after, cb => sub {
533 delete $self->{_tw};
534 $self->_timeout;
535 });
536 } else {
537 delete $self->{_tw};
538 } 891 }
539} 892}
540 893
541############################################################################# 894#############################################################################
542 895
549 902
550The write queue is very simple: you can add data to its end, and 903The write queue is very simple: you can add data to its end, and
551AnyEvent::Handle will automatically try to get rid of it for you. 904AnyEvent::Handle will automatically try to get rid of it for you.
552 905
553When data could be written and the write buffer is shorter then the low 906When data could be written and the write buffer is shorter then the low
554water mark, the C<on_drain> callback will be invoked. 907water mark, the C<on_drain> callback will be invoked once.
555 908
556=over 4 909=over 4
557 910
558=item $handle->on_drain ($cb) 911=item $handle->on_drain ($cb)
559 912
560Sets the C<on_drain> callback or clears it (see the description of 913Sets the C<on_drain> callback or clears it (see the description of
561C<on_drain> in the constructor). 914C<on_drain> in the constructor).
562 915
916This method may invoke callbacks (and therefore the handle might be
917destroyed after it returns).
918
563=cut 919=cut
564 920
565sub on_drain { 921sub on_drain {
566 my ($self, $cb) = @_; 922 my ($self, $cb) = @_;
567 923
571 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf}); 927 if $cb && $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf});
572} 928}
573 929
574=item $handle->push_write ($data) 930=item $handle->push_write ($data)
575 931
576Queues the given scalar to be written. You can push as much data as you 932Queues the given scalar to be written. You can push as much data as
577want (only limited by the available memory), as C<AnyEvent::Handle> 933you want (only limited by the available memory and C<wbuf_max>), as
578buffers it independently of the kernel. 934C<AnyEvent::Handle> buffers it independently of the kernel.
935
936This method may invoke callbacks (and therefore the handle might be
937destroyed after it returns).
579 938
580=cut 939=cut
581 940
582sub _drain_wbuf { 941sub _drain_wbuf {
583 my ($self) = @_; 942 my ($self) = @_;
587 Scalar::Util::weaken $self; 946 Scalar::Util::weaken $self;
588 947
589 my $cb = sub { 948 my $cb = sub {
590 my $len = syswrite $self->{fh}, $self->{wbuf}; 949 my $len = syswrite $self->{fh}, $self->{wbuf};
591 950
592 if ($len >= 0) { 951 if (defined $len) {
593 substr $self->{wbuf}, 0, $len, ""; 952 substr $self->{wbuf}, 0, $len, "";
594 953
595 $self->{_activity} = AnyEvent->now; 954 $self->{_activity} = $self->{_wactivity} = AE::now;
596 955
597 $self->{on_drain}($self) 956 $self->{on_drain}($self)
598 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf}) 957 if $self->{low_water_mark} >= (length $self->{wbuf}) + (length $self->{_tls_wbuf})
599 && $self->{on_drain}; 958 && $self->{on_drain};
600 959
601 delete $self->{_ww} unless length $self->{wbuf}; 960 delete $self->{_ww} unless length $self->{wbuf};
602 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 961 } elsif ($! != EAGAIN && $! != EINTR && $! != EWOULDBLOCK && $! != WSAEWOULDBLOCK) {
603 $self->_error ($!, 1); 962 $self->_error ($!, 1);
604 } 963 }
605 }; 964 };
606 965
607 # try to write data immediately 966 # try to write data immediately
608 $cb->() unless $self->{autocork}; 967 $cb->() unless $self->{autocork};
609 968
610 # if still data left in wbuf, we need to poll 969 # if still data left in wbuf, we need to poll
611 $self->{_ww} = AnyEvent->io (fh => $self->{fh}, poll => "w", cb => $cb) 970 $self->{_ww} = AE::io $self->{fh}, 1, $cb
612 if length $self->{wbuf}; 971 if length $self->{wbuf};
972
973 if (
974 defined $self->{wbuf_max}
975 && $self->{wbuf_max} < length $self->{wbuf}
976 ) {
977 $self->_error (Errno::ENOSPC, 1), return;
978 }
613 }; 979 };
614} 980}
615 981
616our %WH; 982our %WH;
617 983
984# deprecated
618sub register_write_type($$) { 985sub register_write_type($$) {
619 $WH{$_[0]} = $_[1]; 986 $WH{$_[0]} = $_[1];
620} 987}
621 988
622sub push_write { 989sub push_write {
623 my $self = shift; 990 my $self = shift;
624 991
625 if (@_ > 1) { 992 if (@_ > 1) {
626 my $type = shift; 993 my $type = shift;
627 994
995 @_ = ($WH{$type} ||= _load_func "$type\::anyevent_write_type"
628 @_ = ($WH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_write") 996 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_write")
629 ->($self, @_); 997 ->($self, @_);
630 } 998 }
631 999
1000 # we downgrade here to avoid hard-to-track-down bugs,
1001 # and diagnose the problem earlier and better.
1002
632 if ($self->{tls}) { 1003 if ($self->{tls}) {
633 $self->{_tls_wbuf} .= $_[0]; 1004 utf8::downgrade $self->{_tls_wbuf} .= $_[0];
634 1005 &_dotls ($self) if $self->{fh};
635 &_dotls ($self);
636 } else { 1006 } else {
637 $self->{wbuf} .= $_[0]; 1007 utf8::downgrade $self->{wbuf} .= $_[0];
638 $self->_drain_wbuf; 1008 $self->_drain_wbuf if $self->{fh};
639 } 1009 }
640} 1010}
641 1011
642=item $handle->push_write (type => @args) 1012=item $handle->push_write (type => @args)
643 1013
644Instead of formatting your data yourself, you can also let this module do 1014Instead of formatting your data yourself, you can also let this module
645the job by specifying a type and type-specific arguments. 1015do the job by specifying a type and type-specific arguments. You
1016can also specify the (fully qualified) name of a package, in which
1017case AnyEvent tries to load the package and then expects to find the
1018C<anyevent_write_type> function inside (see "custom write types", below).
646 1019
647Predefined types are (if you have ideas for additional types, feel free to 1020Predefined types are (if you have ideas for additional types, feel free to
648drop by and tell us): 1021drop by and tell us):
649 1022
650=over 4 1023=over 4
681 1054
682Encodes the given hash or array reference into a JSON object. Unless you 1055Encodes the given hash or array reference into a JSON object. Unless you
683provide your own JSON object, this means it will be encoded to JSON text 1056provide your own JSON object, this means it will be encoded to JSON text
684in UTF-8. 1057in UTF-8.
685 1058
1059The default encoder might or might not handle every type of JSON value -
1060it might be limited to arrays and objects for security reasons. See the
1061C<json> constructor attribute for more details.
1062
686JSON objects (and arrays) are self-delimiting, so you can write JSON at 1063JSON objects (and arrays) are self-delimiting, so if you only use arrays
687one end of a handle and read them at the other end without using any 1064and hashes, you can write JSON at one end of a handle and read them at the
688additional framing. 1065other end without using any additional framing.
689 1066
690The generated JSON text is guaranteed not to contain any newlines: While 1067The JSON text generated by the default encoder is guaranteed not to
691this module doesn't need delimiters after or between JSON texts to be 1068contain any newlines: While this module doesn't need delimiters after or
692able to read them, many other languages depend on that. 1069between JSON texts to be able to read them, many other languages depend on
1070them.
693 1071
694A simple RPC protocol that interoperates easily with others is to send 1072A simple RPC protocol that interoperates easily with other languages is
695JSON arrays (or objects, although arrays are usually the better choice as 1073to send JSON arrays (or objects, although arrays are usually the better
696they mimic how function argument passing works) and a newline after each 1074choice as they mimic how function argument passing works) and a newline
697JSON text: 1075after each JSON text:
698 1076
699 $handle->push_write (json => ["method", "arg1", "arg2"]); # whatever 1077 $handle->push_write (json => ["method", "arg1", "arg2"]); # whatever
700 $handle->push_write ("\012"); 1078 $handle->push_write ("\012");
701 1079
702An AnyEvent::Handle receiver would simply use the C<json> read type and 1080An AnyEvent::Handle receiver would simply use the C<json> read type and
705 $handle->push_read (json => sub { my $array = $_[1]; ... }); 1083 $handle->push_read (json => sub { my $array = $_[1]; ... });
706 1084
707Other languages could read single lines terminated by a newline and pass 1085Other languages could read single lines terminated by a newline and pass
708this line into their JSON decoder of choice. 1086this line into their JSON decoder of choice.
709 1087
1088=item cbor => $perl_scalar
1089
1090Encodes the given scalar into a CBOR value. Unless you provide your own
1091L<CBOR::XS> object, this means it will be encoded to a CBOR string not
1092using any extensions, if possible.
1093
1094CBOR values are self-delimiting, so you can write CBOR at one end of
1095a handle and read them at the other end without using any additional
1096framing.
1097
1098A simple nd very very fast RPC protocol that interoperates with
1099other languages is to send CBOR and receive CBOR values (arrays are
1100recommended):
1101
1102 $handle->push_write (cbor => ["method", "arg1", "arg2"]); # whatever
1103
1104An AnyEvent::Handle receiver would simply use the C<cbor> read type:
1105
1106 $handle->push_read (cbor => sub { my $array = $_[1]; ... });
1107
710=cut 1108=cut
1109
1110sub json_coder() {
1111 eval { require JSON::XS; JSON::XS->new->utf8 }
1112 || do { require JSON::PP; JSON::PP->new->utf8 }
1113}
711 1114
712register_write_type json => sub { 1115register_write_type json => sub {
713 my ($self, $ref) = @_; 1116 my ($self, $ref) = @_;
714 1117
715 require JSON; 1118 ($self->{json} ||= json_coder)
1119 ->encode ($ref)
1120};
716 1121
717 $self->{json} ? $self->{json}->encode ($ref) 1122sub cbor_coder() {
718 : JSON::encode_json ($ref) 1123 require CBOR::XS;
1124 CBOR::XS->new
1125}
1126
1127register_write_type cbor => sub {
1128 my ($self, $scalar) = @_;
1129
1130 ($self->{cbor} ||= cbor_coder)
1131 ->encode ($scalar)
719}; 1132};
720 1133
721=item storable => $reference 1134=item storable => $reference
722 1135
723Freezes the given reference using L<Storable> and writes it to the 1136Freezes the given reference using L<Storable> and writes it to the
726=cut 1139=cut
727 1140
728register_write_type storable => sub { 1141register_write_type storable => sub {
729 my ($self, $ref) = @_; 1142 my ($self, $ref) = @_;
730 1143
731 require Storable; 1144 require Storable unless $Storable::VERSION;
732 1145
733 pack "w/a*", Storable::nfreeze ($ref) 1146 pack "w/a*", Storable::nfreeze ($ref)
734}; 1147};
735 1148
736=back 1149=back
741before it was actually written. One way to do that is to replace your 1154before it was actually written. One way to do that is to replace your
742C<on_drain> handler by a callback that shuts down the socket (and set 1155C<on_drain> handler by a callback that shuts down the socket (and set
743C<low_water_mark> to C<0>). This method is a shorthand for just that, and 1156C<low_water_mark> to C<0>). This method is a shorthand for just that, and
744replaces the C<on_drain> callback with: 1157replaces the C<on_drain> callback with:
745 1158
746 sub { shutdown $_[0]{fh}, 1 } # for push_shutdown 1159 sub { shutdown $_[0]{fh}, 1 }
747 1160
748This simply shuts down the write side and signals an EOF condition to the 1161This simply shuts down the write side and signals an EOF condition to the
749the peer. 1162the peer.
750 1163
751You can rely on the normal read queue and C<on_eof> handling 1164You can rely on the normal read queue and C<on_eof> handling
752afterwards. This is the cleanest way to close a connection. 1165afterwards. This is the cleanest way to close a connection.
753 1166
1167This method may invoke callbacks (and therefore the handle might be
1168destroyed after it returns).
1169
754=cut 1170=cut
755 1171
756sub push_shutdown { 1172sub push_shutdown {
757 my ($self) = @_; 1173 my ($self) = @_;
758 1174
759 delete $self->{low_water_mark}; 1175 delete $self->{low_water_mark};
760 $self->on_drain (sub { shutdown $_[0]{fh}, 1 }); 1176 $self->on_drain (sub { shutdown $_[0]{fh}, 1 });
761} 1177}
762 1178
763=item AnyEvent::Handle::register_write_type type => $coderef->($handle, @args) 1179=item custom write types - Package::anyevent_write_type $handle, @args
764 1180
765This function (not method) lets you add your own types to C<push_write>. 1181Instead of one of the predefined types, you can also specify the name of
1182a package. AnyEvent will try to load the package and then expects to find
1183a function named C<anyevent_write_type> inside. If it isn't found, it
1184progressively tries to load the parent package until it either finds the
1185function (good) or runs out of packages (bad).
1186
766Whenever the given C<type> is used, C<push_write> will invoke the code 1187Whenever the given C<type> is used, C<push_write> will the function with
767reference with the handle object and the remaining arguments. 1188the handle object and the remaining arguments.
768 1189
769The code reference is supposed to return a single octet string that will 1190The function is supposed to return a single octet string that will be
770be appended to the write buffer. 1191appended to the write buffer, so you can mentally treat this function as a
1192"arguments to on-the-wire-format" converter.
771 1193
772Note that this is a function, and all types registered this way will be 1194Example: implement a custom write type C<join> that joins the remaining
773global, so try to use unique names. 1195arguments using the first one.
1196
1197 $handle->push_write (My::Type => " ", 1,2,3);
1198
1199 # uses the following package, which can be defined in the "My::Type" or in
1200 # the "My" modules to be auto-loaded, or just about anywhere when the
1201 # My::Type::anyevent_write_type is defined before invoking it.
1202
1203 package My::Type;
1204
1205 sub anyevent_write_type {
1206 my ($handle, $delim, @args) = @_;
1207
1208 join $delim, @args
1209 }
774 1210
775=cut 1211=cut
776 1212
777############################################################################# 1213#############################################################################
778 1214
787ways, the "simple" way, using only C<on_read> and the "complex" way, using 1223ways, the "simple" way, using only C<on_read> and the "complex" way, using
788a queue. 1224a queue.
789 1225
790In the simple case, you just install an C<on_read> callback and whenever 1226In the simple case, you just install an C<on_read> callback and whenever
791new data arrives, it will be called. You can then remove some data (if 1227new data arrives, it will be called. You can then remove some data (if
792enough is there) from the read buffer (C<< $handle->rbuf >>). Or you cna 1228enough is there) from the read buffer (C<< $handle->rbuf >>). Or you can
793leave the data there if you want to accumulate more (e.g. when only a 1229leave the data there if you want to accumulate more (e.g. when only a
794partial message has been received so far). 1230partial message has been received so far), or change the read queue with
1231e.g. C<push_read>.
795 1232
796In the more complex case, you want to queue multiple callbacks. In this 1233In the more complex case, you want to queue multiple callbacks. In this
797case, AnyEvent::Handle will call the first queued callback each time new 1234case, AnyEvent::Handle will call the first queued callback each time new
798data arrives (also the first time it is queued) and removes it when it has 1235data arrives (also the first time it is queued) and remove it when it has
799done its job (see C<push_read>, below). 1236done its job (see C<push_read>, below).
800 1237
801This way you can, for example, push three line-reads, followed by reading 1238This way you can, for example, push three line-reads, followed by reading
802a chunk of data, and AnyEvent::Handle will execute them in order. 1239a chunk of data, and AnyEvent::Handle will execute them in order.
803 1240
860=cut 1297=cut
861 1298
862sub _drain_rbuf { 1299sub _drain_rbuf {
863 my ($self) = @_; 1300 my ($self) = @_;
864 1301
1302 # avoid recursion
1303 return if $self->{_skip_drain_rbuf};
865 local $self->{_in_drain} = 1; 1304 local $self->{_skip_drain_rbuf} = 1;
866
867 if (
868 defined $self->{rbuf_max}
869 && $self->{rbuf_max} < length $self->{rbuf}
870 ) {
871 $self->_error (&Errno::ENOSPC, 1), return;
872 }
873 1305
874 while () { 1306 while () {
875 # we need to use a separate tls read buffer, as we must not receive data while 1307 # we need to use a separate tls read buffer, as we must not receive data while
876 # we are draining the buffer, and this can only happen with TLS. 1308 # we are draining the buffer, and this can only happen with TLS.
877 $self->{rbuf} .= delete $self->{_tls_rbuf} if exists $self->{_tls_rbuf}; 1309 $self->{rbuf} .= delete $self->{_tls_rbuf}
1310 if exists $self->{_tls_rbuf};
878 1311
879 my $len = length $self->{rbuf}; 1312 my $len = length $self->{rbuf};
880 1313
881 if (my $cb = shift @{ $self->{_queue} }) { 1314 if (my $cb = shift @{ $self->{_queue} }) {
882 unless ($cb->($self)) { 1315 unless ($cb->($self)) {
883 if ($self->{_eof}) { 1316 # no progress can be made
884 # no progress can be made (not enough data and no data forthcoming) 1317 # (not enough data and no data forthcoming)
885 $self->_error (&Errno::EPIPE, 1), return; 1318 $self->_error (Errno::EPIPE, 1), return
886 } 1319 if $self->{_eof};
887 1320
888 unshift @{ $self->{_queue} }, $cb; 1321 unshift @{ $self->{_queue} }, $cb;
889 last; 1322 last;
890 } 1323 }
891 } elsif ($self->{on_read}) { 1324 } elsif ($self->{on_read}) {
898 && !@{ $self->{_queue} } # and the queue is still empty 1331 && !@{ $self->{_queue} } # and the queue is still empty
899 && $self->{on_read} # but we still have on_read 1332 && $self->{on_read} # but we still have on_read
900 ) { 1333 ) {
901 # no further data will arrive 1334 # no further data will arrive
902 # so no progress can be made 1335 # so no progress can be made
903 $self->_error (&Errno::EPIPE, 1), return 1336 $self->_error (Errno::EPIPE, 1), return
904 if $self->{_eof}; 1337 if $self->{_eof};
905 1338
906 last; # more data might arrive 1339 last; # more data might arrive
907 } 1340 }
908 } else { 1341 } else {
911 last; 1344 last;
912 } 1345 }
913 } 1346 }
914 1347
915 if ($self->{_eof}) { 1348 if ($self->{_eof}) {
916 if ($self->{on_eof}) { 1349 $self->{on_eof}
917 $self->{on_eof}($self) 1350 ? $self->{on_eof}($self)
918 } else {
919 $self->_error (0, 1, "Unexpected end-of-file"); 1351 : $self->_error (0, 1, "Unexpected end-of-file");
920 } 1352
1353 return;
1354 }
1355
1356 if (
1357 defined $self->{rbuf_max}
1358 && $self->{rbuf_max} < length $self->{rbuf}
1359 ) {
1360 $self->_error (Errno::ENOSPC, 1), return;
921 } 1361 }
922 1362
923 # may need to restart read watcher 1363 # may need to restart read watcher
924 unless ($self->{_rw}) { 1364 unless ($self->{_rw}) {
925 $self->start_read 1365 $self->start_read
931 1371
932This replaces the currently set C<on_read> callback, or clears it (when 1372This replaces the currently set C<on_read> callback, or clears it (when
933the new callback is C<undef>). See the description of C<on_read> in the 1373the new callback is C<undef>). See the description of C<on_read> in the
934constructor. 1374constructor.
935 1375
1376This method may invoke callbacks (and therefore the handle might be
1377destroyed after it returns).
1378
936=cut 1379=cut
937 1380
938sub on_read { 1381sub on_read {
939 my ($self, $cb) = @_; 1382 my ($self, $cb) = @_;
940 1383
941 $self->{on_read} = $cb; 1384 $self->{on_read} = $cb;
942 $self->_drain_rbuf if $cb && !$self->{_in_drain}; 1385 $self->_drain_rbuf if $cb;
943} 1386}
944 1387
945=item $handle->rbuf 1388=item $handle->rbuf
946 1389
947Returns the read buffer (as a modifiable lvalue). 1390Returns the read buffer (as a modifiable lvalue). You can also access the
1391read buffer directly as the C<< ->{rbuf} >> member, if you want (this is
1392much faster, and no less clean).
948 1393
949You can access the read buffer directly as the C<< ->{rbuf} >> 1394The only operation allowed on the read buffer (apart from looking at it)
950member, if you want. However, the only operation allowed on the 1395is removing data from its beginning. Otherwise modifying or appending to
951read buffer (apart from looking at it) is removing data from its 1396it is not allowed and will lead to hard-to-track-down bugs.
952beginning. Otherwise modifying or appending to it is not allowed and will
953lead to hard-to-track-down bugs.
954 1397
955NOTE: The read buffer should only be used or modified if the C<on_read>, 1398NOTE: The read buffer should only be used or modified in the C<on_read>
956C<push_read> or C<unshift_read> methods are used. The other read methods 1399callback or when C<push_read> or C<unshift_read> are used with a single
957automatically manage the read buffer. 1400callback (i.e. untyped). Typed C<push_read> and C<unshift_read> methods
1401will manage the read buffer on their own.
958 1402
959=cut 1403=cut
960 1404
961sub rbuf : lvalue { 1405sub rbuf : lvalue {
962 $_[0]{rbuf} 1406 $_[0]{rbuf}
979 1423
980If enough data was available, then the callback must remove all data it is 1424If enough data was available, then the callback must remove all data it is
981interested in (which can be none at all) and return a true value. After returning 1425interested in (which can be none at all) and return a true value. After returning
982true, it will be removed from the queue. 1426true, it will be removed from the queue.
983 1427
1428These methods may invoke callbacks (and therefore the handle might be
1429destroyed after it returns).
1430
984=cut 1431=cut
985 1432
986our %RH; 1433our %RH;
987 1434
988sub register_read_type($$) { 1435sub register_read_type($$) {
994 my $cb = pop; 1441 my $cb = pop;
995 1442
996 if (@_) { 1443 if (@_) {
997 my $type = shift; 1444 my $type = shift;
998 1445
1446 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
999 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::push_read") 1447 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::push_read")
1000 ->($self, $cb, @_); 1448 ->($self, $cb, @_);
1001 } 1449 }
1002 1450
1003 push @{ $self->{_queue} }, $cb; 1451 push @{ $self->{_queue} }, $cb;
1004 $self->_drain_rbuf unless $self->{_in_drain}; 1452 $self->_drain_rbuf;
1005} 1453}
1006 1454
1007sub unshift_read { 1455sub unshift_read {
1008 my $self = shift; 1456 my $self = shift;
1009 my $cb = pop; 1457 my $cb = pop;
1010 1458
1011 if (@_) { 1459 if (@_) {
1012 my $type = shift; 1460 my $type = shift;
1013 1461
1462 $cb = ($RH{$type} ||= _load_func "$type\::anyevent_read_type"
1014 $cb = ($RH{$type} or Carp::croak "unsupported type passed to AnyEvent::Handle::unshift_read") 1463 or Carp::croak "unsupported/unloadable type '$type' passed to AnyEvent::Handle::unshift_read")
1015 ->($self, $cb, @_); 1464 ->($self, $cb, @_);
1016 } 1465 }
1017 1466
1018
1019 unshift @{ $self->{_queue} }, $cb; 1467 unshift @{ $self->{_queue} }, $cb;
1020 $self->_drain_rbuf unless $self->{_in_drain}; 1468 $self->_drain_rbuf;
1021} 1469}
1022 1470
1023=item $handle->push_read (type => @args, $cb) 1471=item $handle->push_read (type => @args, $cb)
1024 1472
1025=item $handle->unshift_read (type => @args, $cb) 1473=item $handle->unshift_read (type => @args, $cb)
1026 1474
1027Instead of providing a callback that parses the data itself you can chose 1475Instead of providing a callback that parses the data itself you can chose
1028between a number of predefined parsing formats, for chunks of data, lines 1476between a number of predefined parsing formats, for chunks of data, lines
1029etc. 1477etc. You can also specify the (fully qualified) name of a package, in
1478which case AnyEvent tries to load the package and then expects to find the
1479C<anyevent_read_type> function inside (see "custom read types", below).
1030 1480
1031Predefined types are (if you have ideas for additional types, feel free to 1481Predefined types are (if you have ideas for additional types, feel free to
1032drop by and tell us): 1482drop by and tell us):
1033 1483
1034=over 4 1484=over 4
1040data. 1490data.
1041 1491
1042Example: read 2 bytes. 1492Example: read 2 bytes.
1043 1493
1044 $handle->push_read (chunk => 2, sub { 1494 $handle->push_read (chunk => 2, sub {
1045 warn "yay ", unpack "H*", $_[1]; 1495 say "yay " . unpack "H*", $_[1];
1046 }); 1496 });
1047 1497
1048=cut 1498=cut
1049 1499
1050register_read_type chunk => sub { 1500register_read_type chunk => sub {
1080 1530
1081register_read_type line => sub { 1531register_read_type line => sub {
1082 my ($self, $cb, $eol) = @_; 1532 my ($self, $cb, $eol) = @_;
1083 1533
1084 if (@_ < 3) { 1534 if (@_ < 3) {
1085 # this is more than twice as fast as the generic code below 1535 # this is faster then the generic code below
1086 sub { 1536 sub {
1087 $_[0]{rbuf} =~ s/^([^\015\012]*)(\015?\012)// or return; 1537 (my $pos = index $_[0]{rbuf}, "\012") >= 0
1538 or return;
1088 1539
1540 (my $str = substr $_[0]{rbuf}, 0, $pos + 1, "") =~ s/(\015?\012)\Z// or die;
1089 $cb->($_[0], $1, $2); 1541 $cb->($_[0], $str, "$1");
1090 1 1542 1
1091 } 1543 }
1092 } else { 1544 } else {
1093 $eol = quotemeta $eol unless ref $eol; 1545 $eol = quotemeta $eol unless ref $eol;
1094 $eol = qr|^(.*?)($eol)|s; 1546 $eol = qr|^(.*?)($eol)|s;
1095 1547
1096 sub { 1548 sub {
1097 $_[0]{rbuf} =~ s/$eol// or return; 1549 $_[0]{rbuf} =~ s/$eol// or return;
1098 1550
1099 $cb->($_[0], $1, $2); 1551 $cb->($_[0], "$1", "$2");
1100 1 1552 1
1101 } 1553 }
1102 } 1554 }
1103}; 1555};
1104 1556
1105=item regex => $accept[, $reject[, $skip], $cb->($handle, $data) 1557=item regex => $accept[, $reject[, $skip], $cb->($handle, $data)
1106 1558
1107Makes a regex match against the regex object C<$accept> and returns 1559Makes a regex match against the regex object C<$accept> and returns
1108everything up to and including the match. 1560everything up to and including the match. All the usual regex variables
1561($1, %+ etc.) from the regex match are available in the callback.
1109 1562
1110Example: read a single line terminated by '\n'. 1563Example: read a single line terminated by '\n'.
1111 1564
1112 $handle->push_read (regex => qr<\n>, sub { ... }); 1565 $handle->push_read (regex => qr<\n>, sub { ... });
1113 1566
1126the receive buffer when neither C<$accept> nor C<$reject> match, 1579the receive buffer when neither C<$accept> nor C<$reject> match,
1127and everything preceding and including the match will be accepted 1580and everything preceding and including the match will be accepted
1128unconditionally. This is useful to skip large amounts of data that you 1581unconditionally. This is useful to skip large amounts of data that you
1129know cannot be matched, so that the C<$accept> or C<$reject> regex do not 1582know cannot be matched, so that the C<$accept> or C<$reject> regex do not
1130have to start matching from the beginning. This is purely an optimisation 1583have to start matching from the beginning. This is purely an optimisation
1131and is usually worth only when you expect more than a few kilobytes. 1584and is usually worth it only when you expect more than a few kilobytes.
1132 1585
1133Example: expect a http header, which ends at C<\015\012\015\012>. Since we 1586Example: expect a http header, which ends at C<\015\012\015\012>. Since we
1134expect the header to be very large (it isn't in practise, but...), we use 1587expect the header to be very large (it isn't in practice, but...), we use
1135a skip regex to skip initial portions. The skip regex is tricky in that 1588a skip regex to skip initial portions. The skip regex is tricky in that
1136it only accepts something not ending in either \015 or \012, as these are 1589it only accepts something not ending in either \015 or \012, as these are
1137required for the accept regex. 1590required for the accept regex.
1138 1591
1139 $handle->push_read (regex => 1592 $handle->push_read (regex =>
1152 1605
1153 sub { 1606 sub {
1154 # accept 1607 # accept
1155 if ($$rbuf =~ $accept) { 1608 if ($$rbuf =~ $accept) {
1156 $data .= substr $$rbuf, 0, $+[0], ""; 1609 $data .= substr $$rbuf, 0, $+[0], "";
1157 $cb->($self, $data); 1610 $cb->($_[0], $data);
1158 return 1; 1611 return 1;
1159 } 1612 }
1160 1613
1161 # reject 1614 # reject
1162 if ($reject && $$rbuf =~ $reject) { 1615 if ($reject && $$rbuf =~ $reject) {
1163 $self->_error (&Errno::EBADMSG); 1616 $_[0]->_error (Errno::EBADMSG);
1164 } 1617 }
1165 1618
1166 # skip 1619 # skip
1167 if ($skip && $$rbuf =~ $skip) { 1620 if ($skip && $$rbuf =~ $skip) {
1168 $data .= substr $$rbuf, 0, $+[0], ""; 1621 $data .= substr $$rbuf, 0, $+[0], "";
1184 my ($self, $cb) = @_; 1637 my ($self, $cb) = @_;
1185 1638
1186 sub { 1639 sub {
1187 unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) { 1640 unless ($_[0]{rbuf} =~ s/^(0|[1-9][0-9]*)://) {
1188 if ($_[0]{rbuf} =~ /[^0-9]/) { 1641 if ($_[0]{rbuf} =~ /[^0-9]/) {
1189 $self->_error (&Errno::EBADMSG); 1642 $_[0]->_error (Errno::EBADMSG);
1190 } 1643 }
1191 return; 1644 return;
1192 } 1645 }
1193 1646
1194 my $len = $1; 1647 my $len = $1;
1195 1648
1196 $self->unshift_read (chunk => $len, sub { 1649 $_[0]->unshift_read (chunk => $len, sub {
1197 my $string = $_[1]; 1650 my $string = $_[1];
1198 $_[0]->unshift_read (chunk => 1, sub { 1651 $_[0]->unshift_read (chunk => 1, sub {
1199 if ($_[1] eq ",") { 1652 if ($_[1] eq ",") {
1200 $cb->($_[0], $string); 1653 $cb->($_[0], $string);
1201 } else { 1654 } else {
1202 $self->_error (&Errno::EBADMSG); 1655 $_[0]->_error (Errno::EBADMSG);
1203 } 1656 }
1204 }); 1657 });
1205 }); 1658 });
1206 1659
1207 1 1660 1
1257=item json => $cb->($handle, $hash_or_arrayref) 1710=item json => $cb->($handle, $hash_or_arrayref)
1258 1711
1259Reads a JSON object or array, decodes it and passes it to the 1712Reads a JSON object or array, decodes it and passes it to the
1260callback. When a parse error occurs, an C<EBADMSG> error will be raised. 1713callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1261 1714
1262If a C<json> object was passed to the constructor, then that will be used 1715If a C<json> object was passed to the constructor, then that will be
1263for the final decode, otherwise it will create a JSON coder expecting UTF-8. 1716used for the final decode, otherwise it will create a L<JSON::XS> or
1717L<JSON::PP> coder object expecting UTF-8.
1264 1718
1265This read type uses the incremental parser available with JSON version 1719This read type uses the incremental parser available with JSON version
12662.09 (and JSON::XS version 2.2) and above. You have to provide a 17202.09 (and JSON::XS version 2.2) and above.
1267dependency on your own: this module will load the JSON module, but
1268AnyEvent does not depend on it itself.
1269 1721
1270Since JSON texts are fully self-delimiting, the C<json> read and write 1722Since JSON texts are fully self-delimiting, the C<json> read and write
1271types are an ideal simple RPC protocol: just exchange JSON datagrams. See 1723types are an ideal simple RPC protocol: just exchange JSON datagrams. See
1272the C<json> write type description, above, for an actual example. 1724the C<json> write type description, above, for an actual example.
1273 1725
1274=cut 1726=cut
1275 1727
1276register_read_type json => sub { 1728register_read_type json => sub {
1277 my ($self, $cb) = @_; 1729 my ($self, $cb) = @_;
1278 1730
1279 my $json = $self->{json} ||= 1731 my $json = $self->{json} ||= json_coder;
1280 eval { require JSON::XS; JSON::XS->new->utf8 }
1281 || do { require JSON; JSON->new->utf8 };
1282 1732
1283 my $data; 1733 my $data;
1284 my $rbuf = \$self->{rbuf};
1285 1734
1286 sub { 1735 sub {
1287 my $ref = eval { $json->incr_parse ($self->{rbuf}) }; 1736 my $ref = eval { $json->incr_parse ($_[0]{rbuf}) };
1288 1737
1289 if ($ref) { 1738 if ($ref) {
1290 $self->{rbuf} = $json->incr_text; 1739 $_[0]{rbuf} = $json->incr_text;
1291 $json->incr_text = ""; 1740 $json->incr_text = "";
1292 $cb->($self, $ref); 1741 $cb->($_[0], $ref);
1293 1742
1294 1 1743 1
1295 } elsif ($@) { 1744 } elsif ($@) {
1296 # error case 1745 # error case
1297 $json->incr_skip; 1746 $json->incr_skip;
1298 1747
1299 $self->{rbuf} = $json->incr_text; 1748 $_[0]{rbuf} = $json->incr_text;
1300 $json->incr_text = ""; 1749 $json->incr_text = "";
1301 1750
1302 $self->_error (&Errno::EBADMSG); 1751 $_[0]->_error (Errno::EBADMSG);
1303 1752
1304 () 1753 ()
1305 } else { 1754 } else {
1306 $self->{rbuf} = ""; 1755 $_[0]{rbuf} = "";
1307 1756
1757 ()
1758 }
1759 }
1760};
1761
1762=item cbor => $cb->($handle, $scalar)
1763
1764Reads a CBOR value, decodes it and passes it to the callback. When a parse
1765error occurs, an C<EBADMSG> error will be raised.
1766
1767If a L<CBOR::XS> object was passed to the constructor, then that will be
1768used for the final decode, otherwise it will create a CBOR coder without
1769enabling any options.
1770
1771You have to provide a dependency to L<CBOR::XS> on your own: this module
1772will load the L<CBOR::XS> module, but AnyEvent does not depend on it
1773itself.
1774
1775Since CBOR values are fully self-delimiting, the C<cbor> read and write
1776types are an ideal simple RPC protocol: just exchange CBOR datagrams. See
1777the C<cbor> write type description, above, for an actual example.
1778
1779=cut
1780
1781register_read_type cbor => sub {
1782 my ($self, $cb) = @_;
1783
1784 my $cbor = $self->{cbor} ||= cbor_coder;
1785
1786 my $data;
1787
1788 sub {
1789 my (@value) = eval { $cbor->incr_parse ($_[0]{rbuf}) };
1790
1791 if (@value) {
1792 $cb->($_[0], @value);
1793
1794 1
1795 } elsif ($@) {
1796 # error case
1797 $cbor->incr_reset;
1798
1799 $_[0]->_error (Errno::EBADMSG);
1800
1801 ()
1802 } else {
1308 () 1803 ()
1309 } 1804 }
1310 } 1805 }
1311}; 1806};
1312 1807
1321=cut 1816=cut
1322 1817
1323register_read_type storable => sub { 1818register_read_type storable => sub {
1324 my ($self, $cb) = @_; 1819 my ($self, $cb) = @_;
1325 1820
1326 require Storable; 1821 require Storable unless $Storable::VERSION;
1327 1822
1328 sub { 1823 sub {
1329 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method 1824 # when we can use 5.10 we can use ".", but for 5.8 we use the re-pack method
1330 defined (my $len = eval { unpack "w", $_[0]{rbuf} }) 1825 defined (my $len = eval { unpack "w", $_[0]{rbuf} })
1331 or return; 1826 or return;
1334 1829
1335 # bypass unshift if we already have the remaining chunk 1830 # bypass unshift if we already have the remaining chunk
1336 if ($format + $len <= length $_[0]{rbuf}) { 1831 if ($format + $len <= length $_[0]{rbuf}) {
1337 my $data = substr $_[0]{rbuf}, $format, $len; 1832 my $data = substr $_[0]{rbuf}, $format, $len;
1338 substr $_[0]{rbuf}, 0, $format + $len, ""; 1833 substr $_[0]{rbuf}, 0, $format + $len, "";
1834
1339 $cb->($_[0], Storable::thaw ($data)); 1835 eval { $cb->($_[0], Storable::thaw ($data)); 1 }
1836 or return $_[0]->_error (Errno::EBADMSG);
1340 } else { 1837 } else {
1341 # remove prefix 1838 # remove prefix
1342 substr $_[0]{rbuf}, 0, $format, ""; 1839 substr $_[0]{rbuf}, 0, $format, "";
1343 1840
1344 # read remaining chunk 1841 # read remaining chunk
1345 $_[0]->unshift_read (chunk => $len, sub { 1842 $_[0]->unshift_read (chunk => $len, sub {
1346 if (my $ref = eval { Storable::thaw ($_[1]) }) { 1843 eval { $cb->($_[0], Storable::thaw ($_[1])); 1 }
1347 $cb->($_[0], $ref);
1348 } else {
1349 $self->_error (&Errno::EBADMSG); 1844 or $_[0]->_error (Errno::EBADMSG);
1350 }
1351 }); 1845 });
1352 } 1846 }
1353 1847
1354 1 1848 1
1355 } 1849 }
1356}; 1850};
1357 1851
1852=item tls_detect => $cb->($handle, $detect, $major, $minor)
1853
1854Checks the input stream for a valid SSL or TLS handshake TLSPaintext
1855record without consuming anything. Only SSL version 3 or higher
1856is handled, up to the fictituous protocol 4.x (but both SSL3+ and
1857SSL2-compatible framing is supported).
1858
1859If it detects that the input data is likely TLS, it calls the callback
1860with a true value for C<$detect> and the (on-wire) TLS version as second
1861and third argument (C<$major> is C<3>, and C<$minor> is 0..3 for SSL
18623.0, TLS 1.0, 1.1 and 1.2, respectively). If it detects the input to
1863be definitely not TLS, it calls the callback with a false value for
1864C<$detect>.
1865
1866The callback could use this information to decide whether or not to start
1867TLS negotiation.
1868
1869In all cases the data read so far is passed to the following read
1870handlers.
1871
1872Usually you want to use the C<tls_autostart> read type instead.
1873
1874If you want to design a protocol that works in the presence of TLS
1875dtection, make sure that any non-TLS data doesn't start with the octet 22
1876(ASCII SYN, 16 hex) or 128-255 (i.e. highest bit set). The checks this
1877read type does are a bit more strict, but might losen in the future to
1878accomodate protocol changes.
1879
1880This read type does not rely on L<AnyEvent::TLS> (and thus, not on
1881L<Net::SSLeay>).
1882
1883=item tls_autostart => [$tls_ctx, ]$tls
1884
1885Tries to detect a valid SSL or TLS handshake. If one is detected, it tries
1886to start tls by calling C<starttls> with the given arguments.
1887
1888In practise, C<$tls> must be C<accept>, or a Net::SSLeay context that has
1889been configured to accept, as servers do not normally send a handshake on
1890their own and ths cannot be detected in this way.
1891
1892See C<tls_detect> above for more details.
1893
1894Example: give the client a chance to start TLS before accepting a text
1895line.
1896
1897 $hdl->push_read (tls_autostart => "accept");
1898 $hdl->push_read (line => sub {
1899 print "received ", ($_[0]{tls} ? "encrypted" : "cleartext"), " <$_[1]>\n";
1900 });
1901
1902=cut
1903
1904register_read_type tls_detect => sub {
1905 my ($self, $cb) = @_;
1906
1907 sub {
1908 # this regex matches a full or partial tls record
1909 if (
1910 # ssl3+: type(22=handshake) major(=3) minor(any) length_hi
1911 $self->{rbuf} =~ /^(?:\z| \x16 (\z| [\x03\x04] (?:\z| . (?:\z| [\x00-\x40] ))))/xs
1912 # ssl2 comapatible: len_hi len_lo type(1) major minor dummy(forlength)
1913 or $self->{rbuf} =~ /^(?:\z| [\x80-\xff] (?:\z| . (?:\z| \x01 (\z| [\x03\x04] (?:\z| . (?:\z| . ))))))/xs
1914 ) {
1915 return if 3 != length $1; # partial match, can't decide yet
1916
1917 # full match, valid TLS record
1918 my ($major, $minor) = unpack "CC", $1;
1919 $cb->($self, "accept", $major + $minor * 0.1);
1920 } else {
1921 # mismatch == guaranteed not TLS
1922 $cb->($self, undef);
1923 }
1924
1925 1
1926 }
1927};
1928
1929register_read_type tls_autostart => sub {
1930 my ($self, @tls) = @_;
1931
1932 $RH{tls_detect}($self, sub {
1933 return unless $_[1];
1934 $_[0]->starttls (@tls);
1935 })
1936};
1937
1358=back 1938=back
1359 1939
1360=item AnyEvent::Handle::register_read_type type => $coderef->($handle, $cb, @args) 1940=item custom read types - Package::anyevent_read_type $handle, $cb, @args
1361 1941
1362This function (not method) lets you add your own types to C<push_read>. 1942Instead of one of the predefined types, you can also specify the name
1943of a package. AnyEvent will try to load the package and then expects to
1944find a function named C<anyevent_read_type> inside. If it isn't found, it
1945progressively tries to load the parent package until it either finds the
1946function (good) or runs out of packages (bad).
1363 1947
1364Whenever the given C<type> is used, C<push_read> will invoke the code 1948Whenever this type is used, C<push_read> will invoke the function with the
1365reference with the handle object, the callback and the remaining 1949handle object, the original callback and the remaining arguments.
1366arguments.
1367 1950
1368The code reference is supposed to return a callback (usually a closure) 1951The function is supposed to return a callback (usually a closure) that
1369that works as a plain read callback (see C<< ->push_read ($cb) >>). 1952works as a plain read callback (see C<< ->push_read ($cb) >>), so you can
1953mentally treat the function as a "configurable read type to read callback"
1954converter.
1370 1955
1371It should invoke the passed callback when it is done reading (remember to 1956It should invoke the original callback when it is done reading (remember
1372pass C<$handle> as first argument as all other callbacks do that). 1957to pass C<$handle> as first argument as all other callbacks do that,
1958although there is no strict requirement on this).
1373 1959
1374Note that this is a function, and all types registered this way will be
1375global, so try to use unique names.
1376
1377For examples, see the source of this module (F<perldoc -m AnyEvent::Handle>, 1960For examples, see the source of this module (F<perldoc -m
1378search for C<register_read_type>)). 1961AnyEvent::Handle>, search for C<register_read_type>)).
1379 1962
1380=item $handle->stop_read 1963=item $handle->stop_read
1381 1964
1382=item $handle->start_read 1965=item $handle->start_read
1383 1966
1389Note that AnyEvent::Handle will automatically C<start_read> for you when 1972Note that AnyEvent::Handle will automatically C<start_read> for you when
1390you change the C<on_read> callback or push/unshift a read callback, and it 1973you change the C<on_read> callback or push/unshift a read callback, and it
1391will automatically C<stop_read> for you when neither C<on_read> is set nor 1974will automatically C<stop_read> for you when neither C<on_read> is set nor
1392there are any read requests in the queue. 1975there are any read requests in the queue.
1393 1976
1394These methods will have no effect when in TLS mode (as TLS doesn't support 1977In older versions of this module (<= 5.3), these methods had no effect,
1395half-duplex connections). 1978as TLS does not support half-duplex connections. In current versions they
1979work as expected, as this behaviour is required to avoid certain resource
1980attacks, where the program would be forced to read (and buffer) arbitrary
1981amounts of data before being able to send some data. The drawback is that
1982some readings of the the SSL/TLS specifications basically require this
1983attack to be working, as SSL/TLS implementations might stall sending data
1984during a rehandshake.
1985
1986As a guideline, during the initial handshake, you should not stop reading,
1987and as a client, it might cause problems, depending on your application.
1396 1988
1397=cut 1989=cut
1398 1990
1399sub stop_read { 1991sub stop_read {
1400 my ($self) = @_; 1992 my ($self) = @_;
1401 1993
1402 delete $self->{_rw} unless $self->{tls}; 1994 delete $self->{_rw};
1403} 1995}
1404 1996
1405sub start_read { 1997sub start_read {
1406 my ($self) = @_; 1998 my ($self) = @_;
1407 1999
1408 unless ($self->{_rw} || $self->{_eof}) { 2000 unless ($self->{_rw} || $self->{_eof} || !$self->{fh}) {
1409 Scalar::Util::weaken $self; 2001 Scalar::Util::weaken $self;
1410 2002
1411 $self->{_rw} = AnyEvent->io (fh => $self->{fh}, poll => "r", cb => sub { 2003 $self->{_rw} = AE::io $self->{fh}, 0, sub {
1412 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf}); 2004 my $rbuf = \($self->{tls} ? my $buf : $self->{rbuf});
1413 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size} || 8192, length $$rbuf; 2005 my $len = sysread $self->{fh}, $$rbuf, $self->{read_size}, length $$rbuf;
1414 2006
1415 if ($len > 0) { 2007 if ($len > 0) {
1416 $self->{_activity} = AnyEvent->now; 2008 $self->{_activity} = $self->{_ractivity} = AE::now;
1417 2009
1418 if ($self->{tls}) { 2010 if ($self->{tls}) {
1419 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf); 2011 Net::SSLeay::BIO_write ($self->{_rbio}, $$rbuf);
1420 2012
1421 &_dotls ($self); 2013 &_dotls ($self);
1422 } else { 2014 } else {
1423 $self->_drain_rbuf unless $self->{_in_drain}; 2015 $self->_drain_rbuf;
2016 }
2017
2018 if ($len == $self->{read_size}) {
2019 $self->{read_size} *= 2;
2020 $self->{read_size} = $self->{max_read_size} || MAX_READ_SIZE
2021 if $self->{read_size} > ($self->{max_read_size} || MAX_READ_SIZE);
1424 } 2022 }
1425 2023
1426 } elsif (defined $len) { 2024 } elsif (defined $len) {
1427 delete $self->{_rw}; 2025 delete $self->{_rw};
1428 $self->{_eof} = 1; 2026 $self->{_eof} = 1;
1429 $self->_drain_rbuf unless $self->{_in_drain}; 2027 $self->_drain_rbuf;
1430 2028
1431 } elsif ($! != EAGAIN && $! != EINTR && $! != WSAEWOULDBLOCK) { 2029 } elsif ($! != EAGAIN && $! != EINTR && $! != EWOULDBLOCK && $! != WSAEWOULDBLOCK) {
1432 return $self->_error ($!, 1); 2030 return $self->_error ($!, 1);
1433 } 2031 }
1434 }); 2032 };
1435 } 2033 }
1436} 2034}
1437 2035
1438our $ERROR_SYSCALL; 2036our $ERROR_SYSCALL;
1439our $ERROR_WANT_READ; 2037our $ERROR_WANT_READ;
1442 my ($self, $err) = @_; 2040 my ($self, $err) = @_;
1443 2041
1444 return $self->_error ($!, 1) 2042 return $self->_error ($!, 1)
1445 if $err == Net::SSLeay::ERROR_SYSCALL (); 2043 if $err == Net::SSLeay::ERROR_SYSCALL ();
1446 2044
1447 my $err =Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ()); 2045 my $err = Net::SSLeay::ERR_error_string (Net::SSLeay::ERR_get_error ());
1448 2046
1449 # reduce error string to look less scary 2047 # reduce error string to look less scary
1450 $err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /; 2048 $err =~ s/^error:[0-9a-fA-F]{8}:[^:]+:([^:]+):/\L$1: /;
1451 2049
1452 if ($self->{_on_starttls}) { 2050 if ($self->{_on_starttls}) {
1453 (delete $self->{_on_starttls})->($self, undef, $err); 2051 (delete $self->{_on_starttls})->($self, undef, $err);
1454 &_freetls; 2052 &_freetls;
1455 } else { 2053 } else {
1456 &_freetls; 2054 &_freetls;
1457 $self->_error (&Errno::EPROTO, 1, $err); 2055 $self->_error (Errno::EPROTO, 1, $err);
1458 } 2056 }
1459} 2057}
1460 2058
1461# poll the write BIO and send the data if applicable 2059# poll the write BIO and send the data if applicable
1462# also decode read data if possible 2060# also decode read data if possible
1466sub _dotls { 2064sub _dotls {
1467 my ($self) = @_; 2065 my ($self) = @_;
1468 2066
1469 my $tmp; 2067 my $tmp;
1470 2068
1471 if (length $self->{_tls_wbuf}) { 2069 while (length $self->{_tls_wbuf}) {
1472 while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { 2070 if (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) <= 0) {
1473 substr $self->{_tls_wbuf}, 0, $tmp, ""; 2071 $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp);
2072
2073 return $self->_tls_error ($tmp)
2074 if $tmp != $ERROR_WANT_READ
2075 && ($tmp != $ERROR_SYSCALL || $!);
2076
2077 last;
1474 } 2078 }
1475 2079
1476 $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp); 2080 substr $self->{_tls_wbuf}, 0, $tmp, "";
1477 return $self->_tls_error ($tmp)
1478 if $tmp != $ERROR_WANT_READ
1479 && ($tmp != $ERROR_SYSCALL || $!);
1480 } 2081 }
1481 2082
1482 while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) { 2083 while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) {
1483 unless (length $tmp) { 2084 unless (length $tmp) {
1484 $self->{_on_starttls} 2085 $self->{_on_starttls}
1494 $self->{_eof} = 1; 2095 $self->{_eof} = 1;
1495 } 2096 }
1496 } 2097 }
1497 2098
1498 $self->{_tls_rbuf} .= $tmp; 2099 $self->{_tls_rbuf} .= $tmp;
1499 $self->_drain_rbuf unless $self->{_in_drain}; 2100 $self->_drain_rbuf;
1500 $self->{tls} or return; # tls session might have gone away in callback 2101 $self->{tls} or return; # tls session might have gone away in callback
1501 } 2102 }
1502 2103
1503 $tmp = Net::SSLeay::get_error ($self->{tls}, -1); 2104 $tmp = Net::SSLeay::get_error ($self->{tls}, -1); # -1 is not neccessarily correct, but Net::SSLeay doesn't tell us
1504 return $self->_tls_error ($tmp) 2105 return $self->_tls_error ($tmp)
1505 if $tmp != $ERROR_WANT_READ 2106 if $tmp != $ERROR_WANT_READ
1506 && ($tmp != $ERROR_SYSCALL || $!); 2107 && ($tmp != $ERROR_SYSCALL || $!);
1507 2108
1508 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) { 2109 while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) {
1509 $self->{wbuf} .= $tmp; 2110 $self->{wbuf} .= $tmp;
1510 $self->_drain_wbuf; 2111 $self->_drain_wbuf;
2112 $self->{tls} or return; # tls session might have gone away in callback
1511 } 2113 }
1512 2114
1513 $self->{_on_starttls} 2115 $self->{_on_starttls}
1514 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK () 2116 and Net::SSLeay::state ($self->{tls}) == Net::SSLeay::ST_OK ()
1515 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established"); 2117 and (delete $self->{_on_starttls})->($self, 1, "TLS/SSL connection established");
1517 2119
1518=item $handle->starttls ($tls[, $tls_ctx]) 2120=item $handle->starttls ($tls[, $tls_ctx])
1519 2121
1520Instead of starting TLS negotiation immediately when the AnyEvent::Handle 2122Instead of starting TLS negotiation immediately when the AnyEvent::Handle
1521object is created, you can also do that at a later time by calling 2123object is created, you can also do that at a later time by calling
1522C<starttls>. 2124C<starttls>. See the C<tls> constructor argument for general info.
2125
2126Starting TLS is currently an asynchronous operation - when you push some
2127write data and then call C<< ->starttls >> then TLS negotiation will start
2128immediately, after which the queued write data is then sent. This might
2129change in future versions, so best make sure you have no outstanding write
2130data when calling this method.
1523 2131
1524The first argument is the same as the C<tls> constructor argument (either 2132The first argument is the same as the C<tls> constructor argument (either
1525C<"connect">, C<"accept"> or an existing Net::SSLeay object). 2133C<"connect">, C<"accept"> or an existing Net::SSLeay object).
1526 2134
1527The second argument is the optional C<AnyEvent::TLS> object that is used 2135The second argument is the optional C<AnyEvent::TLS> object that is used
1532The TLS connection object will end up in C<< $handle->{tls} >>, the TLS 2140The TLS connection object will end up in C<< $handle->{tls} >>, the TLS
1533context in C<< $handle->{tls_ctx} >> after this call and can be used or 2141context in C<< $handle->{tls_ctx} >> after this call and can be used or
1534changed to your liking. Note that the handshake might have already started 2142changed to your liking. Note that the handshake might have already started
1535when this function returns. 2143when this function returns.
1536 2144
1537If it an error to start a TLS handshake more than once per 2145Due to bugs in OpenSSL, it might or might not be possible to do multiple
1538AnyEvent::Handle object (this is due to bugs in OpenSSL). 2146handshakes on the same stream. It is best to not attempt to use the
2147stream after stopping TLS.
2148
2149This method may invoke callbacks (and therefore the handle might be
2150destroyed after it returns).
1539 2151
1540=cut 2152=cut
1541 2153
1542our %TLS_CACHE; #TODO not yet documented, should we? 2154our %TLS_CACHE; #TODO not yet documented, should we?
1543 2155
1544sub starttls { 2156sub starttls {
1545 my ($self, $ssl, $ctx) = @_; 2157 my ($self, $tls, $ctx) = @_;
1546 2158
1547 require Net::SSLeay; 2159 Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught"
1548
1549 Carp::croak "it is an error to call starttls more than once on an AnyEvent::Handle object"
1550 if $self->{tls}; 2160 if $self->{tls};
2161
2162 unless (defined $AnyEvent::TLS::VERSION) {
2163 eval {
2164 require Net::SSLeay;
2165 require AnyEvent::TLS;
2166 1
2167 } or return $self->_error (Errno::EPROTO, 1, "TLS support not available on this system");
2168 }
2169
2170 $self->{tls} = $tls;
2171 $self->{tls_ctx} = $ctx if @_ > 2;
2172
2173 return unless $self->{fh};
1551 2174
1552 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL (); 2175 $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL ();
1553 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ (); 2176 $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ ();
1554 2177
2178 $tls = delete $self->{tls};
1555 $ctx ||= $self->{tls_ctx}; 2179 $ctx = $self->{tls_ctx};
2180
2181 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session
1556 2182
1557 if ("HASH" eq ref $ctx) { 2183 if ("HASH" eq ref $ctx) {
1558 require AnyEvent::TLS;
1559
1560 local $Carp::CarpLevel = 1; # skip ourselves when creating a new context
1561
1562 if ($ctx->{cache}) { 2184 if ($ctx->{cache}) {
1563 my $key = $ctx+0; 2185 my $key = $ctx+0;
1564 $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx; 2186 $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx;
1565 } else { 2187 } else {
1566 $ctx = new AnyEvent::TLS %$ctx; 2188 $ctx = new AnyEvent::TLS %$ctx;
1567 } 2189 }
1568 } 2190 }
1569 2191
1570 $self->{tls_ctx} = $ctx || TLS_CTX (); 2192 $self->{tls_ctx} = $ctx || TLS_CTX ();
1571 $self->{tls} = $ssl = $self->{tls_ctx}->_get_session ($ssl, $self, $self->{peername}); 2193 $self->{tls} = $tls = $self->{tls_ctx}->_get_session ($tls, $self, $self->{peername});
1572 2194
1573 # basically, this is deep magic (because SSL_read should have the same issues) 2195 # basically, this is deep magic (because SSL_read should have the same issues)
1574 # but the openssl maintainers basically said: "trust us, it just works". 2196 # but the openssl maintainers basically said: "trust us, it just works".
1575 # (unfortunately, we have to hardcode constants because the abysmally misdesigned 2197 # (unfortunately, we have to hardcode constants because the abysmally misdesigned
1576 # and mismaintained ssleay-module doesn't even offer them). 2198 # and mismaintained ssleay-module doesn't even offer them).
1583 # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to 2205 # and we drive openssl fully in blocking mode here. Or maybe we don't - openssl seems to
1584 # have identity issues in that area. 2206 # have identity issues in that area.
1585# Net::SSLeay::CTX_set_mode ($ssl, 2207# Net::SSLeay::CTX_set_mode ($ssl,
1586# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1) 2208# (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
1587# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2)); 2209# | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
1588 Net::SSLeay::CTX_set_mode ($ssl, 1|2); 2210 Net::SSLeay::CTX_set_mode ($tls, 1|2);
1589 2211
1590 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 2212 $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1591 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ()); 2213 $self->{_wbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());
1592 2214
2215 Net::SSLeay::BIO_write ($self->{_rbio}, $self->{rbuf});
2216 $self->{rbuf} = "";
2217
1593 Net::SSLeay::set_bio ($ssl, $self->{_rbio}, $self->{_wbio}); 2218 Net::SSLeay::set_bio ($tls, $self->{_rbio}, $self->{_wbio});
1594 2219
1595 $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) } 2220 $self->{_on_starttls} = sub { $_[0]{on_starttls}(@_) }
1596 if $self->{on_starttls}; 2221 if $self->{on_starttls};
1597 2222
1598 &_dotls; # need to trigger the initial handshake 2223 &_dotls; # need to trigger the initial handshake
1601 2226
1602=item $handle->stoptls 2227=item $handle->stoptls
1603 2228
1604Shuts down the SSL connection - this makes a proper EOF handshake by 2229Shuts down the SSL connection - this makes a proper EOF handshake by
1605sending a close notify to the other side, but since OpenSSL doesn't 2230sending a close notify to the other side, but since OpenSSL doesn't
1606support non-blocking shut downs, it is not possible to re-use the stream 2231support non-blocking shut downs, it is not guaranteed that you can re-use
1607afterwards. 2232the stream afterwards.
2233
2234This method may invoke callbacks (and therefore the handle might be
2235destroyed after it returns).
1608 2236
1609=cut 2237=cut
1610 2238
1611sub stoptls { 2239sub stoptls {
1612 my ($self) = @_; 2240 my ($self) = @_;
1613 2241
1614 if ($self->{tls}) { 2242 if ($self->{tls} && $self->{fh}) {
1615 Net::SSLeay::shutdown ($self->{tls}); 2243 Net::SSLeay::shutdown ($self->{tls});
1616 2244
1617 &_dotls; 2245 &_dotls;
1618 2246
1619# # we don't give a shit. no, we do, but we can't. no...#d# 2247# # we don't give a shit. no, we do, but we can't. no...#d#
1625sub _freetls { 2253sub _freetls {
1626 my ($self) = @_; 2254 my ($self) = @_;
1627 2255
1628 return unless $self->{tls}; 2256 return unless $self->{tls};
1629 2257
1630 $self->{tls_ctx}->_put_session (delete $self->{tls}); 2258 $self->{tls_ctx}->_put_session (delete $self->{tls})
2259 if $self->{tls} > 0;
1631 2260
1632 delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)}; 2261 delete @$self{qw(_rbio _wbio _tls_wbuf _on_starttls)};
1633} 2262}
1634 2263
2264=item $handle->resettls
2265
2266This rarely-used method simply resets and TLS state on the handle, usually
2267causing data loss.
2268
2269One case where it may be useful is when you want to skip over the data in
2270the stream but you are not interested in interpreting it, so data loss is
2271no concern.
2272
2273=cut
2274
2275*resettls = \&_freetls;
2276
1635sub DESTROY { 2277sub DESTROY {
1636 my ($self) = @_; 2278 my ($self) = @_;
1637 2279
1638 &_freetls; 2280 &_freetls;
1639 2281
1640 my $linger = exists $self->{linger} ? $self->{linger} : 3600; 2282 my $linger = exists $self->{linger} ? $self->{linger} : 3600;
1641 2283
1642 if ($linger && length $self->{wbuf}) { 2284 if ($linger && length $self->{wbuf} && $self->{fh}) {
1643 my $fh = delete $self->{fh}; 2285 my $fh = delete $self->{fh};
1644 my $wbuf = delete $self->{wbuf}; 2286 my $wbuf = delete $self->{wbuf};
1645 2287
1646 my @linger; 2288 my @linger;
1647 2289
1648 push @linger, AnyEvent->io (fh => $fh, poll => "w", cb => sub { 2290 push @linger, AE::io $fh, 1, sub {
1649 my $len = syswrite $fh, $wbuf, length $wbuf; 2291 my $len = syswrite $fh, $wbuf, length $wbuf;
1650 2292
1651 if ($len > 0) { 2293 if ($len > 0) {
1652 substr $wbuf, 0, $len, ""; 2294 substr $wbuf, 0, $len, "";
1653 } else { 2295 } elsif (defined $len || ($! != EAGAIN && $! != EINTR && $! != EWOULDBLOCK && $! != WSAEWOULDBLOCK)) {
1654 @linger = (); # end 2296 @linger = (); # end
1655 } 2297 }
1656 }); 2298 };
1657 push @linger, AnyEvent->timer (after => $linger, cb => sub { 2299 push @linger, AE::timer $linger, 0, sub {
1658 @linger = (); 2300 @linger = ();
1659 }); 2301 };
1660 } 2302 }
1661} 2303}
1662 2304
1663=item $handle->destroy 2305=item $handle->destroy
1664 2306
1665Shuts down the handle object as much as possible - this call ensures that 2307Shuts down the handle object as much as possible - this call ensures that
1666no further callbacks will be invoked and as many resources as possible 2308no further callbacks will be invoked and as many resources as possible
1667will be freed. You must not call any methods on the object afterwards. 2309will be freed. Any method you will call on the handle object after
2310destroying it in this way will be silently ignored (and it will return the
2311empty list).
1668 2312
1669Normally, you can just "forget" any references to an AnyEvent::Handle 2313Normally, you can just "forget" any references to an AnyEvent::Handle
1670object and it will simply shut down. This works in fatal error and EOF 2314object and it will simply shut down. This works in fatal error and EOF
1671callbacks, as well as code outside. It does I<NOT> work in a read or write 2315callbacks, as well as code outside. It does I<NOT> work in a read or write
1672callback, so when you want to destroy the AnyEvent::Handle object from 2316callback, so when you want to destroy the AnyEvent::Handle object from
1673within such an callback. You I<MUST> call C<< ->destroy >> explicitly in 2317within such an callback. You I<MUST> call C<< ->destroy >> explicitly in
1674that case. 2318that case.
1675 2319
2320Destroying the handle object in this way has the advantage that callbacks
2321will be removed as well, so if those are the only reference holders (as
2322is common), then one doesn't need to do anything special to break any
2323reference cycles.
2324
1676The handle might still linger in the background and write out remaining 2325The handle might still linger in the background and write out remaining
1677data, as specified by the C<linger> option, however. 2326data, as specified by the C<linger> option, however.
1678 2327
1679=cut 2328=cut
1680 2329
1681sub destroy { 2330sub destroy {
1682 my ($self) = @_; 2331 my ($self) = @_;
1683 2332
1684 $self->DESTROY; 2333 $self->DESTROY;
1685 %$self = (); 2334 %$self = ();
2335 bless $self, "AnyEvent::Handle::destroyed";
1686} 2336}
2337
2338sub AnyEvent::Handle::destroyed::AUTOLOAD {
2339 #nop
2340}
2341
2342=item $handle->destroyed
2343
2344Returns false as long as the handle hasn't been destroyed by a call to C<<
2345->destroy >>, true otherwise.
2346
2347Can be useful to decide whether the handle is still valid after some
2348callback possibly destroyed the handle. For example, C<< ->push_write >>,
2349C<< ->starttls >> and other methods can call user callbacks, which in turn
2350can destroy the handle, so work can be avoided by checking sometimes:
2351
2352 $hdl->starttls ("accept");
2353 return if $hdl->destroyed;
2354 $hdl->push_write (...
2355
2356Note that the call to C<push_write> will silently be ignored if the handle
2357has been destroyed, so often you can just ignore the possibility of the
2358handle being destroyed.
2359
2360=cut
2361
2362sub destroyed { 0 }
2363sub AnyEvent::Handle::destroyed::destroyed { 1 }
1687 2364
1688=item AnyEvent::Handle::TLS_CTX 2365=item AnyEvent::Handle::TLS_CTX
1689 2366
1690This function creates and returns the AnyEvent::TLS object used by default 2367This function creates and returns the AnyEvent::TLS object used by default
1691for TLS mode. 2368for TLS mode.
1719 2396
1720It is only safe to "forget" the reference inside EOF or error callbacks, 2397It is only safe to "forget" the reference inside EOF or error callbacks,
1721from within all other callbacks, you need to explicitly call the C<< 2398from within all other callbacks, you need to explicitly call the C<<
1722->destroy >> method. 2399->destroy >> method.
1723 2400
2401=item Why is my C<on_eof> callback never called?
2402
2403Probably because your C<on_error> callback is being called instead: When
2404you have outstanding requests in your read queue, then an EOF is
2405considered an error as you clearly expected some data.
2406
2407To avoid this, make sure you have an empty read queue whenever your handle
2408is supposed to be "idle" (i.e. connection closes are O.K.). You can set
2409an C<on_read> handler that simply pushes the first read requests in the
2410queue.
2411
2412See also the next question, which explains this in a bit more detail.
2413
2414=item How can I serve requests in a loop?
2415
2416Most protocols consist of some setup phase (authentication for example)
2417followed by a request handling phase, where the server waits for requests
2418and handles them, in a loop.
2419
2420There are two important variants: The first (traditional, better) variant
2421handles requests until the server gets some QUIT command, causing it to
2422close the connection first (highly desirable for a busy TCP server). A
2423client dropping the connection is an error, which means this variant can
2424detect an unexpected detection close.
2425
2426To handle this case, always make sure you have a non-empty read queue, by
2427pushing the "read request start" handler on it:
2428
2429 # we assume a request starts with a single line
2430 my @start_request; @start_request = (line => sub {
2431 my ($hdl, $line) = @_;
2432
2433 ... handle request
2434
2435 # push next request read, possibly from a nested callback
2436 $hdl->push_read (@start_request);
2437 });
2438
2439 # auth done, now go into request handling loop
2440 # now push the first @start_request
2441 $hdl->push_read (@start_request);
2442
2443By always having an outstanding C<push_read>, the handle always expects
2444some data and raises the C<EPIPE> error when the connction is dropped
2445unexpectedly.
2446
2447The second variant is a protocol where the client can drop the connection
2448at any time. For TCP, this means that the server machine may run out of
2449sockets easier, and in general, it means you cannot distinguish a protocl
2450failure/client crash from a normal connection close. Nevertheless, these
2451kinds of protocols are common (and sometimes even the best solution to the
2452problem).
2453
2454Having an outstanding read request at all times is possible if you ignore
2455C<EPIPE> errors, but this doesn't help with when the client drops the
2456connection during a request, which would still be an error.
2457
2458A better solution is to push the initial request read in an C<on_read>
2459callback. This avoids an error, as when the server doesn't expect data
2460(i.e. is idly waiting for the next request, an EOF will not raise an
2461error, but simply result in an C<on_eof> callback. It is also a bit slower
2462and simpler:
2463
2464 # auth done, now go into request handling loop
2465 $hdl->on_read (sub {
2466 my ($hdl) = @_;
2467
2468 # called each time we receive data but the read queue is empty
2469 # simply start read the request
2470
2471 $hdl->push_read (line => sub {
2472 my ($hdl, $line) = @_;
2473
2474 ... handle request
2475
2476 # do nothing special when the request has been handled, just
2477 # let the request queue go empty.
2478 });
2479 });
2480
1724=item I get different callback invocations in TLS mode/Why can't I pause 2481=item I get different callback invocations in TLS mode/Why can't I pause
1725reading? 2482reading?
1726 2483
1727Unlike, say, TCP, TLS connections do not consist of two independent 2484Unlike, say, TCP, TLS connections do not consist of two independent
1728communication channels, one for each direction. Or put differently. The 2485communication channels, one for each direction. Or put differently, the
1729read and write directions are not independent of each other: you cannot 2486read and write directions are not independent of each other: you cannot
1730write data unless you are also prepared to read, and vice versa. 2487write data unless you are also prepared to read, and vice versa.
1731 2488
1732This can mean than, in TLS mode, you might get C<on_error> or C<on_eof> 2489This means that, in TLS mode, you might get C<on_error> or C<on_eof>
1733callback invocations when you are not expecting any read data - the reason 2490callback invocations when you are not expecting any read data - the reason
1734is that AnyEvent::Handle always reads in TLS mode. 2491is that AnyEvent::Handle always reads in TLS mode.
1735 2492
1736During the connection, you have to make sure that you always have a 2493During the connection, you have to make sure that you always have a
1737non-empty read-queue, or an C<on_read> watcher. At the end of the 2494non-empty read-queue, or an C<on_read> watcher. At the end of the
1747 2504
1748 $handle->on_read (sub { }); 2505 $handle->on_read (sub { });
1749 $handle->on_eof (undef); 2506 $handle->on_eof (undef);
1750 $handle->on_error (sub { 2507 $handle->on_error (sub {
1751 my $data = delete $_[0]{rbuf}; 2508 my $data = delete $_[0]{rbuf};
1752 undef $handle;
1753 }); 2509 });
2510
2511Note that this example removes the C<rbuf> member from the handle object,
2512which is not normally allowed by the API. It is expressly permitted in
2513this case only, as the handle object needs to be destroyed afterwards.
1754 2514
1755The reason to use C<on_error> is that TCP connections, due to latencies 2515The reason to use C<on_error> is that TCP connections, due to latencies
1756and packets loss, might get closed quite violently with an error, when in 2516and packets loss, might get closed quite violently with an error, when in
1757fact, all data has been received. 2517fact all data has been received.
1758 2518
1759It is usually better to use acknowledgements when transferring data, 2519It is usually better to use acknowledgements when transferring data,
1760to make sure the other side hasn't just died and you got the data 2520to make sure the other side hasn't just died and you got the data
1761intact. This is also one reason why so many internet protocols have an 2521intact. This is also one reason why so many internet protocols have an
1762explicit QUIT command. 2522explicit QUIT command.
1769C<low_water_mark> this will be called precisely when all data has been 2529C<low_water_mark> this will be called precisely when all data has been
1770written to the socket: 2530written to the socket:
1771 2531
1772 $handle->push_write (...); 2532 $handle->push_write (...);
1773 $handle->on_drain (sub { 2533 $handle->on_drain (sub {
1774 warn "all data submitted to the kernel\n"; 2534 AE::log debug => "All data submitted to the kernel.";
1775 undef $handle; 2535 undef $handle;
1776 }); 2536 });
1777 2537
1778If you just want to queue some data and then signal EOF to the other side, 2538If you just want to queue some data and then signal EOF to the other side,
1779consider using C<< ->push_shutdown >> instead. 2539consider using C<< ->push_shutdown >> instead.
1780 2540
1781=item I want to contact a TLS/SSL server, I don't care about security. 2541=item I want to contact a TLS/SSL server, I don't care about security.
1782 2542
1783If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS, 2543If your TLS server is a pure TLS server (e.g. HTTPS) that only speaks TLS,
1784simply connect to it and then create the AnyEvent::Handle with the C<tls> 2544connect to it and then create the AnyEvent::Handle with the C<tls>
1785parameter: 2545parameter:
1786 2546
1787 tcp_connect $host, $port, sub { 2547 tcp_connect $host, $port, sub {
1788 my ($fh) = @_; 2548 my ($fh) = @_;
1789 2549
1863When you have intermediate CA certificates that your clients might not 2623When you have intermediate CA certificates that your clients might not
1864know about, just append them to the C<cert_file>. 2624know about, just append them to the C<cert_file>.
1865 2625
1866=back 2626=back
1867 2627
1868
1869=head1 SUBCLASSING AnyEvent::Handle 2628=head1 SUBCLASSING AnyEvent::Handle
1870 2629
1871In many cases, you might want to subclass AnyEvent::Handle. 2630In many cases, you might want to subclass AnyEvent::Handle.
1872 2631
1873To make this easier, a given version of AnyEvent::Handle uses these 2632To make this easier, a given version of AnyEvent::Handle uses these
1889 2648
1890=item * all members not documented here and not prefixed with an underscore 2649=item * all members not documented here and not prefixed with an underscore
1891are free to use in subclasses. 2650are free to use in subclasses.
1892 2651
1893Of course, new versions of AnyEvent::Handle may introduce more "public" 2652Of course, new versions of AnyEvent::Handle may introduce more "public"
1894member variables, but thats just life, at least it is documented. 2653member variables, but that's just life. At least it is documented.
1895 2654
1896=back 2655=back
1897 2656
1898=head1 AUTHOR 2657=head1 AUTHOR
1899 2658
1900Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>. 2659Robin Redeker C<< <elmex at ta-sa.org> >>, Marc Lehmann <schmorp@schmorp.de>.
1901 2660
1902=cut 2661=cut
1903 2662
19041; # End of AnyEvent::Handle 26631
2664

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines