--- AnyEvent/Changes 2014/08/28 16:51:20 1.593 +++ AnyEvent/Changes 2015/06/28 09:30:37 1.604 @@ -1,10 +1,5 @@ Revision history for Perl extension AnyEvent. -03:55:22 Doku zu new: It is possible to push requests on the read and write queues, and modify properties of the stream, even - while -03:55:23 AnyEvent::Handle is connecting. -03:55:39 doku zu on_connect: It is not allowed to use the read or write queues while the handle object is connecting. - TODO: document TCP_*** constants TODO: add debug/trace logging to some modules TODO: use the eval-with-cb-call trick also to speed up JSON? @@ -13,8 +8,36 @@ TODO: AnyEvent::Handle with AnyEvent::IO? TODO: invalid. and localhost. specialcasing inside AEDNS and not AESocket (rfc6761) TODO: maybe implement env variable to give hosts precedence +TODO: hosts always read? that's not expected +TODO: more formats for parse_ipv6 (single ipv6 address without port, ...p80, ...#80) + + - add a more explicit warning to AnyEvent::Handle that it doesn't + work on files, people keep getting confused. + - new function AnyEvent::Socket::tcp_bind. + - new functions AnyEvent::fh_block and AnyEvent::fh_unblock. + - aligned ipv6 address formatting with RFC 5952 (by not shortening + a single :0: to ::). + - added stability canary support. + +7.09 Sat May 2 16:38:53 CEST 2015 + - AnyEvent::Debug called an internal function (AnyEvent::Log::ft) + that was renamed to AnyEvent::Log:format_time. uinder its old name + (analyzed by Michael Stovenour). + - update AnyEvent::DNS fallback resolver addresses: + seems google effectively killed most other free dns resolvers, + so remove them, but add cable and wireless (ecrc) since it was + stable for 20 years or so, official or not, and there should be + an alternative to google. + - perl5porters broke windows error codes in 5.20, and mapped + WSAEWOULDBLOCK on the (different) EWOULDBLOCK error code, and + WSAEINPROGRESS into the incompatible ERINPROGRESS code, probably + because they were so cool. They probably broke other error codes + for no reason, too, but I didn't care for checking, it's too + depressing. This version only works around the WSAEWOULDBLOCK + issue, because I don't have a nice way to work around the + WSAEINPROGRESS bug. -TODO: improve confess skipping +7.08 Wed Dec 10 05:27:17 CET 2014 - work around a newly introduced bug in Socket 2.011 (an errornous sun_length check) (analyzed by Maxime Soulé). - AnyEvent::TLS didn't load (but refer to) AnyEvent::Socket @@ -25,6 +48,8 @@ certain undocumented behaviour patterns such as not being able to remove a child watch source after it has fired, which we will try to emulate to avoid "criticals". what where they thinking...). + - mention json security issues in AnyEvent::Handle, now that Douglas + Crockford has foolishly and incompatibly changed JSON. - changed default dns resolver "max_outstanding" value from 1 to 10, the latter beinfg the intended value all along (reported by Ilya Chesnokov). @@ -652,7 +677,7 @@ - add an additional error message parameter to AnyEvent::Handle's on_error callback (for TLS, $! is still available). - add AnyEvent::Handle on_starttls/on_stoptls callbacks. - - make AnyEvent::Handle more robust against early conenction + - make AnyEvent::Handle more robust against early connection failures (during new), and return C in that case from the constructor. - AnyEvent::Handle will now try to load only JSON::XS first,