| 1 | Revision history for AnyEvent::MP |
1 | Revision history for AnyEvent::MP |
| 2 | |
2 | |
| 3 | TODO: testsuite |
3 | TODO: testsuite |
| 4 | TODO: intro: maybe simple job pool example? |
4 | TODO: intro: maybe simple job pool example? |
| 5 | TODO: intro: mention watchdog... |
5 | TODO: intro: mention watchdog... |
| 6 | TODO: use gvpe method of making contact, if possible. |
6 | |
| 7 | TODO: explain service sin aemp |
7 | faq: can't se anything |
|
|
8 | faq: all is asynch |
|
|
9 | faq: how to interface to non-perl nodes? |
|
|
10 | |
|
|
11 | TODO: maybe disbale warnings by default? |
|
|
12 | TODO: lese sadrak mails |
|
|
13 | |
|
|
14 | 1.29 Fri May 7 20:13:39 CEST 2010 |
|
|
15 | - codename "Sadrak". |
|
|
16 | - fix error in callback at AnyEvent/MP/Global.pm line 339 |
|
|
17 | (found by Sadrak). |
|
|
18 | - listener-less nodes had trouble sending keepalive |
|
|
19 | messages on write timeouts (found by Sadrak). |
|
|
20 | - the monitor guard could cause a memleak due |
|
|
21 | to autovivification if a mon was cleared after |
|
|
22 | the port was gone (analysed by Sadrak). |
|
|
23 | - do not overwrite the config file if we couldn't read it |
|
|
24 | for some reason (lesson demonstrated by Sadrak). |
|
|
25 | |
|
|
26 | 1.28 Thu Apr 1 21:23:54 CEST 2010 |
|
|
27 | - accepted connections didn't correctly set up the SRCNODE |
|
|
28 | in some cases, leading to intra-node messages (such as monitoring) |
|
|
29 | to fail silently (great testcase by Sadrak). |
|
|
30 | |
|
|
31 | 1.27 Sat Mar 20 21:11:16 CET 2010 |
|
|
32 | - avoid exceptions in the transport code if the connection |
|
|
33 | fails during TLS negotiation. |
|
|
34 | - delay new address broadcasts in seednodes, to reduce the |
|
|
35 | likelyhood of nodes connecting at the same time, leading to |
|
|
36 | message loss. |
|
|
37 | - improve general message passing efficiency by 8%, and special |
|
|
38 | case json framing for a 50% speed increase. |
|
|
39 | - add hints how to interface to aemp nodes from other programming |
|
|
40 | languages using the aemp protocol in AnyEvent::MP::Transport |
|
|
41 | (it can really be quite simple). |
|
|
42 | - handle unsupported remote framings more gracefully. |
|
|
43 | |
|
|
44 | 1.26 Wed Dec 30 16:48:37 CET 2009 |
|
|
45 | - INCOMPATIBLE CHANGE: the high-level node protocol changed, |
|
|
46 | all nodes need to upgrade. |
|
|
47 | - remote kil's did not work (reported by Eugene Grigoriev). |
|
|
48 | - documented monitor_timeout, connect_interval, auth_offer, |
|
|
49 | auth_accept, framing_format, autocork and nodelay options |
|
|
50 | and make them configurable via bin/aemp. |
|
|
51 | - some doc updates. |
|
|
52 | - remote kil's were not synchronous to message sends which affected |
|
|
53 | nobody, as remote kils were broken. |
|
|
54 | - remote mon/unmonitor requests were not synchronous to message |
|
|
55 | sends either sometimes, although it likely didnt matter. |
|
|
56 | |
|
|
57 | 1.24 Wed Dec 9 14:59:52 CET 2009 |
|
|
58 | - codename "the foul egg". |
|
|
59 | - increased "unmonitored local port died" message level to 2, so |
|
|
60 | it is displayed by default now. |
|
|
61 | - generate random seed at configure time, not module loading time, |
|
|
62 | so fork&configure works as expected. |
|
|
63 | - decreased "seed"-related message priority in Global from 0 (d'oh) |
|
|
64 | to 9, as they are not signifcant. |
|
|
65 | - new experimental module AnyEvent::MP::DataConn to establish |
|
|
66 | additional data connections between nodes. |
|
|
67 | - bin/aemp now loads AnyEvent::Watchdog::Util before trying |
|
|
68 | to call restart. |
|
|
69 | - bin/aemp setcert didn't properly handle the filename argument. |
|
|
70 | - removed empty and unused timeout= parameter from protocol greeting. |
| 8 | |
71 | |
| 9 | 1.23 Fri Nov 6 18:46:26 CET 2009 |
72 | 1.23 Fri Nov 6 18:46:26 CET 2009 |
| 10 | - listener-less nodes were misinformed by their masters about |
73 | - listener-less nodes were misinformed by their masters about |
| 11 | the location of new nodes, and therefore didn't connect |
74 | the location of new nodes, and therefore didn't connect |
| 12 | properly in all cases. |
75 | properly in all cases. |
