[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent/Handle.pm

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents):
Revision 1.84 by root, Thu Aug 21 19:13:05 2008 UTC vs.
Revision 1.88 by root, Thu Aug 21 23:48:35 2008 UTC

 AnyEvent::Handle - non-blocking I/O on file handles via AnyEvent
 =cut
-our $VERSION = 4.232;
+our $VERSION = 4.233;
 =head1 SYNOPSIS
    use AnyEvent;
    use AnyEvent::Handle;
 occured, such as not being able to resolve the hostname, failure to
 connect or a read error.
 Some errors are fatal (which is indicated by C<$fatal> being true). On
 fatal errors the handle object will be shut down and will not be usable
-(but you are free to look at the current C< ->rbuf >). Examples of fatal
+(but you are free to look at the current C<< ->rbuf >>). Examples of fatal
 errors are an EOF condition with active (but unsatisifable) read watchers
 (C<EPIPE>) or I/O errors.
 Non-fatal errors can be retried by simply returning, but it is recommended
 to simply ignore this parameter and instead abondon the handle object
 =item timeout => $fractional_seconds
 If non-zero, then this enables an "inactivity" timeout: whenever this many
 seconds pass without a successful read or write on the underlying file
 handle, the C<on_timeout> callback will be invoked (and if that one is
-missing, an C<ETIMEDOUT> error will be raised).
+missing, a non-fatal C<ETIMEDOUT> error will be raised).
 Note that timeout processing is also active when you currently do not have
 any outstanding read or write requests: If you plan to keep the connection
 idle then you should disable the timout temporarily or ignore the timeout
-in the C<on_timeout> callback.
+in the C<on_timeout> callback, in which case AnyEvent::Handle will simply
+restart the timeout.
 Zero (the default) disables this timeout.
 =item on_timeout => $cb->($handle)
 =item rbuf_max => <bytes>
 If defined, then a fatal error will be raised (with C<$!> set to C<ENOSPC>)
 when the read buffer ever (strictly) exceeds this size. This is useful to
-avoid denial-of-service attacks.
+avoid some forms of denial-of-service attacks.
 For example, a server accepting connections from untrusted sources should
 be configured to accept only so-and-so much data that it cannot act on
 (for example, when expecting a line, an attacker could send an unlimited
 amount of data without a callback ever being called as long as the line
 isn't finished).
 =item autocork => <boolean>
 When disabled (the default), then C<push_write> will try to immediately
-write the data to the handle if possible. This avoids having to register
+write the data to the handle, if possible. This avoids having to register
-a write watcher and wait for the next event loop iteration, but can be
+a write watcher and wait for the next event loop iteration, but can
-inefficient if you write multiple small chunks (this disadvantage is
+be inefficient if you write multiple small chunks (on the wire, this
-usually avoided by your kernel's nagle algorithm, see C<low_delay>).
+disadvantage is usually avoided by your kernel's nagle algorithm, see
+C<no_delay>, but this option can save costly syscalls).
 When enabled, then writes will always be queued till the next event loop
 iteration. This is efficient when you do many small writes per iteration,
-but less efficient when you do a single write only.
+but less efficient when you do a single write only per iteration (or when
+the write buffer often is full). It also increases write latency.
 =item no_delay => <boolean>
 When doing small writes on sockets, your operating system kernel might
 wait a bit for more data before actually sending it out. This is called
 the Nagle algorithm, and usually it is beneficial.
-In some situations you want as low a delay as possible, which cna be
+In some situations you want as low a delay as possible, which can be
-accomplishd by setting this option to true.
+accomplishd by setting this option to a true value.
-The default is your opertaing system's default behaviour, this option
+The default is your opertaing system's default behaviour (most likely
-explicitly enables or disables it, if possible.
+enabled), this option explicitly enables or disables it, if possible.
 =item read_size => <bytes>
-The default read block size (the amount of bytes this module will try to read
+The default read block size (the amount of bytes this module will
-during each (loop iteration). Default: C<8192>.
+try to read during each loop iteration, which affects memory
+requirements). Default: C<8192>.
 =item low_water_mark => <bytes>
 Sets the amount of bytes (default: C<0>) that make up an "empty" write
 buffer: If the write reaches this size or gets even samller it is
 considered empty.
+Sometimes it can be beneficial (for performance reasons) to add data to
+the write buffer before it is fully drained, but this is a rare case, as
+the operating system kernel usually buffers data as well, so the default
+is good in almost all cases.
 =item linger => <seconds>
 If non-zero (default: C<3600>), then the destructor of the
-AnyEvent::Handle object will check wether there is still outstanding write
+AnyEvent::Handle object will check whether there is still outstanding
-data and will install a watcher that will write out this data. No errors
+write data and will install a watcher that will write this data to the
-will be reported (this mostly matches how the operating system treats
+socket. No errors will be reported (this mostly matches how the operating
-outstanding data at socket close time).
+system treats outstanding data at socket close time).
-This will not work for partial TLS data that could not yet been
+This will not work for partial TLS data that could not be encoded
-encoded. This data will be lost.
+yet. This data will be lost.
 =item tls => "accept" | "connect" | Net::SSLeay::SSL object
-When this parameter is given, it enables TLS (SSL) mode, that means it
+When this parameter is given, it enables TLS (SSL) mode, that means
-will start making tls handshake and will transparently encrypt/decrypt
+AnyEvent will start a TLS handshake as soon as the conenction has been
-data.
+established and will transparently encrypt/decrypt data afterwards.
 TLS mode requires Net::SSLeay to be installed (it will be loaded
-automatically when you try to create a TLS handle).
+automatically when you try to create a TLS handle): this module doesn't
+have a dependency on that module, so if your module requires it, you have
+to add the dependency yourself.
-For the TLS server side, use C<accept>, and for the TLS client side of a
+Unlike TCP, TLS has a server and client side: for the TLS server side, use
-connection, use C<connect> mode.
+C<accept>, and for the TLS client side of a connection, use C<connect>
+mode.
 You can also provide your own TLS connection object, but you have
 to make sure that you call either C<Net::SSLeay::set_connect_state>
 or C<Net::SSLeay::set_accept_state> on it before you pass it to
 AnyEvent::Handle.
-See the C<starttls> method if you need to start TLS negotiation later.
+See the C<< ->starttls >> method for when need to start TLS negotiation later.
 =item tls_ctx => $ssl_ctx
-Use the given Net::SSLeay::CTX object to create the new TLS connection
+Use the given C<Net::SSLeay::CTX> object to create the new TLS connection
 (unless a connection object was specified directly). If this parameter is
 missing, then AnyEvent::Handle will use C<AnyEvent::Handle::TLS_CTX>.
 =item json => JSON or JSON::XS object
 This is the json coder object used by the C<json> read and write types.
 If you don't supply it, then AnyEvent::Handle will create and use a
-suitable one, which will write and expect UTF-8 encoded JSON texts.
+suitable one (on demand), which will write and expect UTF-8 encoded JSON
+texts.
 Note that you are responsible to depend on the JSON module if you want to
 use this functionality, as AnyEvent does not have a dependency itself.
 =item filter_r => $cb
 =item filter_w => $cb
-These exist, but are undocumented at this time.
+These exist, but are undocumented at this time. (They are used internally
+by the TLS code).
 =back
 =cut
    }
 }
 =item $fh = $handle->fh
-This method returns the file handle of the L<AnyEvent::Handle> object.
+This method returns the file handle used to create the L<AnyEvent::Handle> object.
 =cut
 sub fh { $_[0]{fh} }
    $_[0]{on_eof} = $_[1];
 }
 =item $handle->on_timeout ($cb)
-Replace the current C<on_timeout> callback, or disables the callback
+Replace the current C<on_timeout> callback, or disables the callback (but
-(but not the timeout) if C<$cb> = C<undef>. See C<timeout> constructor
+not the timeout) if C<$cb> = C<undef>. See the C<timeout> constructor
-argument.
+argument and method.
 =cut
 sub on_timeout {
    $_[0]{on_timeout} = $_[1];
    # basically, this is deep magic (because SSL_read should have the same issues)
    # but the openssl maintainers basically said: "trust us, it just works".
    # (unfortunately, we have to hardcode constants because the abysmally misdesigned
    # and mismaintained ssleay-module doesn't even offer them).
    # http://www.mail-archive.com/openssl-dev@openssl.org/msg22420.html
+   #
+   # in short: this is a mess.
+   #
+   # note that we do not try to kepe the length constant between writes as we are required to do.
+   # we assume that most (but not all) of this insanity only applies to non-blocking cases,
+   # and we drive openssl fully in blocking mode here.
    Net::SSLeay::CTX_set_mode ($self->{tls},
       (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ENABLE_PARTIAL_WRITE () } || 1)
       | (eval { local $SIG{__DIE__}; Net::SSLeay::MODE_ACCEPT_MOVING_WRITE_BUFFER () } || 2));
    $self->{_rbio} = Net::SSLeay::BIO_new (Net::SSLeay::BIO_s_mem ());

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents): Revision 1.84 by root, Thu Aug 21 19:13:05 2008 UTC vs. Revision 1.88 by root, Thu Aug 21 23:48:35 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent/Handle.pm (file contents):
Revision 1.84 by root, Thu Aug 21 19:13:05 2008 UTC vs.
Revision 1.88 by root, Thu Aug 21 23:48:35 2008 UTC