ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent/Changes
(Generate patch)

Comparing AnyEvent/Changes (file contents):
Revision 1.146 by root, Wed Jun 4 09:55:16 2008 UTC vs.
Revision 1.161 by root, Thu Jul 3 02:03:33 2008 UTC

1Revision history for Perl extension AnyEvent. 1Revision history for Perl extension AnyEvent.
2 2
34.160 Thu Jul 3 04:02:21 CEST 2008
4 - re-registering signal watchers after unregistering one did
5 not work if a backend falls back on AnyEvent's default
6 implementation (also affected child watchers).
7 - new AnyEvent::Handle options: autocork and no_delay.
8
94.152 Sun Jun 22 14:15:44 CEST 2008
10 - allow for 32-bit perls that implement shifts differently
11 on different architectures in parse_ipv4 (reported and
12 analysed by Keiichi DAIBA).
13
144.151 Fri Jun 6 17:34:24 CEST 2008
15 - make sure specifying _only_ on_read and never pushing reads
16 works.
17
184.15 Fri Jun 6 13:00:46 CEST 2008
19 - the pure perl backend would keep some watchers alive when more than
20 one watcher was registered for the same fd.
21 - new "packstring" and "storable" read and write types
22 for AnyEvent::Handle.
23 - allow on_eof handler to be called after on_error with EPIPE returns.
24 - do not immediately call on_read callback in handle constructor.
25
264.14 Thu Jun 5 20:29:31 CEST 2008
27 - Fixed a bug in DNS SRV priority sorting.
28 - AnyEvent::Util::guard now reports runtime errors while
29 executing the guard block as warnings.
30 - handle 0-byte-reads just before EOF correctly in AnyEvent::Handle.
31
324.13 Thu Jun 5 00:47:59 CEST 2008
3 - AnyEvent::DNS only followed cname chains with length 2, 33 - AnyEvent::DNS only followed cname chains with length 2,
4 contrary to documentation. bumped it up to 10, thanks to 34 contrary to documentation. bumped it up to 10, thanks to
5 microsoft, the current broken-dns-config-king. 35 microsoft, the current broken-dns-config-king.
36 - AnyEvent::DNS didn't check for socket return status
37 but instead relied on perl not creating filehandles in that
38 case - too bad it gives you a bogus file handle (reported
39 and analysed by Vladimir Timofeev).
6 - fix queue management logic in AnyEvent::Handle: 40 - fix queue management logic in AnyEvent::Handle:
7 when on_read was registered, the queue was empty 41 when on_read was registered, the queue was empty
8 and no progress could be made AnyEvent::Handle would 42 and no progress could be made AnyEvent::Handle would
9 enter an endless loop. 43 enter an endless loop.
10 - correctly start reading again when the handle became 44 - correctly start reading again when the handle became

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines