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

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents):
Revision 1.107 by root, Wed Nov 26 06:40:47 2008 UTC vs.
Revision 1.111 by root, Wed Jan 21 06:01:29 2009 UTC

… …
14 14
15AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent 15AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent
16 16
17=cut 17=cut
18 18
19our $VERSION = 4.33; 19our $VERSION = 4.331;
20 20
21=head1 SYNOPSIS 21=head1 SYNOPSIS
22 22
23 use AnyEvent; 23 use AnyEvent;
24 use AnyEvent::Handle; 24 use AnyEvent::Handle;
… …
254 254
255You can also provide your own TLS connection object, but you have 255You can also provide your own TLS connection object, but you have
256to make sure that you call either C<Net::SSLeay::set_connect_state> 256to make sure that you call either C<Net::SSLeay::set_connect_state>
257or C<Net::SSLeay::set_accept_state> on it before you pass it to 257or C<Net::SSLeay::set_accept_state> on it before you pass it to
258AnyEvent::Handle. 258AnyEvent::Handle.
259
260B<IMPORTANT:> since Net::SSLeay "objects" are really only integers,
261passing in the wrong integer will lead to certain crash. This most often
262happens when one uses a stylish C<< tls => 1 >> and is surprised about the
263segmentation fault.
259 264
260See the C<< ->starttls >> method for when need to start TLS negotiation later. 265See the C<< ->starttls >> method for when need to start TLS negotiation later.
261 266
262=item tls_ctx => $ssl_ctx 267=item tls_ctx => $ssl_ctx
263 268
… …
1139 } 1144 }
1140}; 1145};
1141 1146
1142=item json => $cb->($handle, $hash_or_arrayref) 1147=item json => $cb->($handle, $hash_or_arrayref)
1143 1148
1144Reads a JSON object or array, decodes it and passes it to the callback. 1149Reads a JSON object or array, decodes it and passes it to the
1150callback. When a parse error occurs, an C<EBADMSG> error will be raised.
1145 1151
1146If a C<json> object was passed to the constructor, then that will be used 1152If a C<json> object was passed to the constructor, then that will be used
1147for the final decode, otherwise it will create a JSON coder expecting UTF-8. 1153for the final decode, otherwise it will create a JSON coder expecting UTF-8.
1148 1154
1149This read type uses the incremental parser available with JSON version 1155This read type uses the incremental parser available with JSON version
… …
1166 my $rbuf = \$self->{rbuf}; 1172 my $rbuf = \$self->{rbuf};
1167 1173
1168 my $json = $self->{json} ||= JSON->new->utf8; 1174 my $json = $self->{json} ||= JSON->new->utf8;
1169 1175
1170 sub { 1176 sub {
1177 eval {
1171 my $ref = $json->incr_parse ($self->{rbuf}); 1178 my $ref = $json->incr_parse ($self->{rbuf});
1172 1179
1173 if ($ref) { 1180 if ($ref) {
1181 $self->{rbuf} = $json->incr_text;
1182 $json->incr_text = "";
1183 $cb->($self, $ref);
1184
1185 1
1186 } else {
1187 $self->{rbuf} = "";
1188 ()
1189 }
1190
1191 1
1192 } or do {
1193 # error case
1194 $json->incr_skip;
1195
1174 $self->{rbuf} = $json->incr_text; 1196 $self->{rbuf} = $json->incr_text;
1175 $json->incr_text = ""; 1197 $json->incr_text = "";
1176 $cb->($self, $ref);
1177 1198
1178 1 1199 $self->_error (&Errno::EBADMSG);
1179 } else {
1180 $self->{rbuf} = "";
1181 ()
1182 } 1200 };
1201
1183 } 1202 }
1184}; 1203};
1185 1204
1186=item storable => $cb->($handle, $ref) 1205=item storable => $cb->($handle, $ref)
1187 1206

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines