| 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. |
|
|
| 7 | |
6 | |
|
|
7 | 1.26 Wed Dec 30 16:48:37 CET 2009 |
|
|
8 | - INCOMPATIBLE CHANGE: the high-level node protocol changed, |
|
|
9 | all nodes need to upgrade. |
|
|
10 | - remote kil's did not work (reported by Eugene Grigoriev). |
|
|
11 | - documented monitor_timeout, connect_interval, auth_offer, |
|
|
12 | auth_accept, framing_format, autocork and nodelay options |
|
|
13 | and make them configurable via bin/aemp. |
|
|
14 | - some doc updates. |
|
|
15 | - remote kil's were not synchronous to message sends which affected |
|
|
16 | nobody, as remote kils were broken. |
|
|
17 | - remote mon/unmonitor requests were not synchronous to message |
|
|
18 | sends either sometimes, although it likely didnt matter. |
|
|
19 | |
|
|
20 | 1.24 Wed Dec 9 14:59:52 CET 2009 |
|
|
21 | - codename "the foul egg". |
|
|
22 | - increased "unmonitored local port died" message level to 2, so |
|
|
23 | it is displayed by default now. |
|
|
24 | - generate random seed at configure time, not module loading time, |
|
|
25 | so fork&configure works as expected. |
|
|
26 | - decreased "seed"-related message priority in Global from 0 (d'oh) |
|
|
27 | to 9, as they are not signifcant. |
|
|
28 | - new experimental module AnyEvent::MP::DataConn to establish |
|
|
29 | additional data connections between nodes. |
|
|
30 | - bin/aemp now loads AnyEvent::Watchdog::Util before trying |
|
|
31 | to call restart. |
|
|
32 | - bin/aemp setcert didn't properly handle the filename argument. |
|
|
33 | - removed empty and unused timeout= parameter from protocol greeting. |
|
|
34 | |
|
|
35 | 1.23 Fri Nov 6 18:46:26 CET 2009 |
|
|
36 | - listener-less nodes were misinformed by their masters about |
|
|
37 | the location of new nodes, and therefore didn't connect |
|
|
38 | properly in all cases. |
|
|
39 | - messages send during node-up processing could sometimes get lost, |
|
|
40 | which would hamper global's ability to mesh the network. |
| 8 | - fixed AnyEvent::MP::Global::grp_reg to return a guard also |
41 | - fixed AnyEvent::MP::Global::grp_reg to return a guard also |
|
|
42 | in scalar context. |
|
|
43 | - fixed AnyEvent::MP::Kernel::mon_nodes to return a guard also |
| 9 | in scalar context. |
44 | in scalar context. |
| 10 | - try to improve error reporting when automatically loading |
45 | - try to improve error reporting when automatically loading |
| 11 | a function - being unable to load a module will now |
46 | a function - being unable to load a module will now |
| 12 | stop the process and report the error. |
47 | stop the process and report the error. |
| 13 | |
48 | |
