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