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? |
6 | |
7 | |
7 | faq: can't se anything |
8 | faq: can't se anything |
8 | faq: all is asynch |
9 | faq: all is asynch |
9 | faq: how to interface to non-perl nodes? |
10 | faq: how to interface to non-perl nodes? |
10 | |
11 | |
11 | TODO: maybe disbale warnings by default? |
12 | - fixed small typo in AnyEvent::MP::Transport. |
12 | |
13 | |
|
|
14 | 1.30 Thu Jun 30 11:30:39 CEST 2011 |
|
|
15 | - connection errors at the right time would kill node |
|
|
16 | connections in a bad way (patch by Malcolm Studd). |
|
|
17 | |
|
|
18 | 1.29 Fri May 7 20:13:39 CEST 2010 |
|
|
19 | - codename "Sadrak". |
|
|
20 | - fix error in callback at AnyEvent/MP/Global.pm line 339 |
|
|
21 | (found by Sadrak). |
13 | - listener-less nodes had trouble sending keepalive |
22 | - listener-less nodes had trouble sending keepalive |
14 | messages on write timeouts (found by Sadrak). |
23 | messages on write timeouts (found by Sadrak). |
15 | - the monitor guard could cause a memleak due |
24 | - the monitor guard could cause a memleak due |
16 | to autovivification if a mon was cleared after |
25 | to autovivification if a mon was cleared after |
17 | the port was gone (analysed by Sadrak). |
26 | the port was gone (analysed by Sadrak). |
|
|
27 | - do not overwrite the config file if we couldn't read it |
|
|
28 | for some reason (lesson demonstrated by Sadrak). |
18 | |
29 | |
19 | 1.28 Thu Apr 1 21:23:54 CEST 2010 |
30 | 1.28 Thu Apr 1 21:23:54 CEST 2010 |
20 | - accepted conenctions didn't corretcly set up the SRCNODE |
31 | - accepted connections didn't correctly set up the SRCNODE |
21 | in some cases, leading to intra-node messages (such as monitoring) |
32 | in some cases, leading to intra-node messages (such as monitoring) |
22 | to fail silently (great testcase by Sadrak). |
33 | to fail silently (great testcase by Sadrak). |
23 | |
34 | |
24 | 1.27 Sat Mar 20 21:11:16 CET 2010 |
35 | 1.27 Sat Mar 20 21:11:16 CET 2010 |
25 | - avoid exceptions in the transport code if the connection |
36 | - avoid exceptions in the transport code if the connection |