| 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: maybe disbale warnings by default? |
|
|
7 | TODO: networkdomains |
|
|
8 | TODO: group proxy nodes - store group membership for other nodes |
|
|
9 | TODO: switch to AnyEvent::Log |
| 6 | |
10 | |
| 7 | faq: can't se anything |
11 | faq: can't se anything |
| 8 | faq: all is asynch |
12 | faq: all is asynch |
| 9 | faq: how to interface to non-perl nodes? |
13 | faq: how to interface to non-perl nodes? |
| 10 | |
14 | |
| 11 | TODO: maybe disbale warnings by default? |
15 | TODO: Anyevent::MP gets grp_reg, grp_get |
| 12 | TODO: lies sadrak mails |
16 | TODO: AnyEvent::MP keeps list of all "global" nodes |
|
|
17 | TODO: Global loaded on demand only, adds grp database and node address database |
|
|
18 | TODO: transport connects use any global node to find addresses (maybe itself) |
|
|
19 | TODO: not really |
|
|
20 | TODO: configure norc => 1, force => 1 |
| 13 | |
21 | |
|
|
22 | - move seed code to Kernel. |
|
|
23 | - fixed small typo in AnyEvent::MP::Transport. |
|
|
24 | |
|
|
25 | 1.30 Thu Jun 30 11:30:39 CEST 2011 |
|
|
26 | - connection errors at the right time would kill node |
|
|
27 | connections in a bad way (patch by Malcolm Studd). |
|
|
28 | |
|
|
29 | 1.29 Fri May 7 20:13:39 CEST 2010 |
|
|
30 | - codename "Sadrak". |
| 14 | - fix error in callback at AnyEvent/MP/Global.pm line 339 |
31 | - fix error in callback at AnyEvent/MP/Global.pm line 339 |
| 15 | (found by Sadrak). |
32 | (found by Sadrak). |
| 16 | - listener-less nodes had trouble sending keepalive |
33 | - listener-less nodes had trouble sending keepalive |
| 17 | messages on write timeouts (found by Sadrak). |
34 | messages on write timeouts (found by Sadrak). |
| 18 | - the monitor guard could cause a memleak due |
35 | - the monitor guard could cause a memleak due |
| 19 | to autovivification if a mon was cleared after |
36 | to autovivification if a mon was cleared after |
| 20 | the port was gone (analysed by Sadrak). |
37 | the port was gone (analysed by Sadrak). |
|
|
38 | - do not overwrite the config file if we couldn't read it |
|
|
39 | for some reason (lesson demonstrated by Sadrak). |
| 21 | |
40 | |
| 22 | 1.28 Thu Apr 1 21:23:54 CEST 2010 |
41 | 1.28 Thu Apr 1 21:23:54 CEST 2010 |
| 23 | - accepted connections didn't correctly set up the SRCNODE |
42 | - accepted connections didn't correctly set up the SRCNODE |
| 24 | in some cases, leading to intra-node messages (such as monitoring) |
43 | in some cases, leading to intra-node messages (such as monitoring) |
| 25 | to fail silently (great testcase by Sadrak). |
44 | to fail silently (great testcase by Sadrak). |
