--- AnyEvent/Changes 2009/07/15 15:51:06 1.280 +++ AnyEvent/Changes 2009/08/06 13:45:04 1.321 @@ -1,7 +1,91 @@ Revision history for Perl extension AnyEvent. -TODO: implement getprotobyname - - ignore possible spurious wake-ups. +4.91 Thu Aug 6 15:42:45 CEST 2009 + - AE::Handle::starttls could get out of sync when the read buffer + already contains some TLS handshake. + - AE::Handle did not properly free the TLS session, causing bigger + memory leaks in Net::SSLeay than expected (reported by toaster). + - AE::Socket::tcp_connect will now artificially delay invoking + the callback to avoid returning after invoking the callback. + - convert many internal watcher uses to AE API. + +4.9 Sat Aug 1 11:07:01 CEST 2009 + - Glib silently fails when registering a timeout with + a negative value, so avoid that. + - call condvar callback immediately when it is set + after the condition is already signalled. + - check rbuf_max condition only after trying to consume + data. + - normalise signal numbers to names when using the ae's + signal handling, but do not document this (yet). + - pure perl signal emulation did not properly set nonblocking + mode on the signal pipe on win32 (this is unlikely to have caused + any issues). + - new module: AnyEvent::Debug. + - AnyEvent::Strict now checks that a signal was specified + by name (not name or number). + - reduce memory footprint in typical cases by ~50kb by + only compiling signal code when necessary. + - add AnyEvent::Handle->rbuf_max. + - grab the AE namespace for future new API, implement stubs for + said future/alternative API. + - new function: AnyEvent::Socket::format_hostport. + +4.881 Tue Jul 28 12:51:53 CEST 2009 + - work around a bug in local in pre-5.10 perls, causing + AnyEvent::Handle to recurse when it should not + (analyzed by elmex). + +4.88 Tue Jul 28 04:04:37 CEST 2009 + - re-bless the handle into a dummy package after calling + AnyEvent::Handle::destroy, so the user does not need to check + for errors after every push_write etc. + - do not attempt to run t/02_signals.t on obviously broken + platforms. + +4.87 Sun Jul 26 02:06:16 CEST 2009 + - do not attempt to linger when there is no longer a valid fh. + - enforce tls mode to be either accept or connect, do not simply + segfault in Net::SSLeay. + - AnyEvent::Handle can now call tcp_connect itself (new parameters + connect, on_prepare, on_connect and on_connect_error). Updated + tutorial accordingly. + - add AnyEvent::Impl::Irssi backend. + +4.86 Mon Jul 20 23:52:29 CEST 2009 + - since the verbose warning is not enough, explicitly document + that versions before 1.33 of Net::SSLeay are not secure. + - work around signal handling races in Event and (...) Event::Lib. + - try to align signal-race timer to full-second boundaries. + - work around Tk not liking negative timeouts. + - don't complain of different grades of environmental unfriendlyness + in IO::Async. + +4.85 Sat Jul 18 06:16:14 CEST 2009 + - nail the signal race problem in perl once and for all + (see $AnyEvent::MAX_SIGNAL_LATENCY). + - take advantage of Async::Interrupt if it is available. + - load Time::HiRes and Guard modules on demand only. + - add optional/recommended modules section to AnyEvent + documentation. + - reduce memory usage considerably (and reduce startup penalty) + by not using "strict", "warnings" and "overload" modules. + - work around buggy windows/openbsd perls and provide EBADMSG + and EPROTO ourselves when missing. + - improve perl 5.6 compatibility of the core event loop. + - made Net::SSLeay version 1.33 a soft requirement. + +4.83 Fri Jul 17 16:56:26 CEST 2009 + - implement AnyEvent::Socket::getprotobyname. + - AnyEvent::CondVar's will now detect recursive blocking + waits and will croak, as too many people fall into + this trap. + - AnyEvent::Handle will now call ->destroy on itself after + executing the on_error callback, instead of doing some + half-baked internal shutdown, for fatal errors. + - clarify on_eof behaviour w.r.t. the read queue and + on_read callbacks. + - ignore some possible spurious wake-ups in tcp_connect. 4.82 Sat Jul 11 00:34:55 CEST 2009 - POE and Event backends didn't accept some callable objects as