| … | |
… | |
| 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 | TODO: use gvpe method of making contact, if possible. |
|
|
7 | TODO: explain service sin aemp |
| 7 | |
8 | |
| 8 | 1.21 |
9 | 1.23 Fri Nov 6 18:46:26 CET 2009 |
|
|
10 | - listener-less nodes were misinformed by their masters about |
|
|
11 | the location of new nodes, and therefore didn't connect |
|
|
12 | properly in all cases. |
|
|
13 | - messages send during node-up processing could sometimes get lost, |
|
|
14 | which would hamper global's ability to mesh the network. |
|
|
15 | - fixed AnyEvent::MP::Global::grp_reg to return a guard also |
|
|
16 | in scalar context. |
|
|
17 | - fixed AnyEvent::MP::Kernel::mon_nodes to return a guard also |
|
|
18 | in scalar context. |
|
|
19 | - try to improve error reporting when automatically loading |
|
|
20 | a function - being unable to load a module will now |
|
|
21 | stop the process and report the error. |
|
|
22 | |
|
|
23 | 1.22 Sat Oct 17 03:41:47 CEST 2009 |
|
|
24 | - fix two rcv-bugs: after adding a tagged rcv, the default |
|
|
25 | callback would not be used or changed anymore (reported |
|
|
26 | by Felix Antonius Wilhelm Ostmann, with apologies for |
|
|
27 | taking so long to releae the fix). |
|
|
28 | - added Coro::MP introduction to AnyEvent::MP::Intro. |
|
|
29 | - add peval function. |
|
|
30 | |
|
|
31 | 1.21 Mon Oct 5 21:58:36 CEST 2009 |
| 9 | - always delay kil messages. |
32 | - always delay kil messages. |
|
|
33 | - remote monitor requests were never cleaned up (found by |
|
|
34 | Sadrak and analysed by elmex). |
|
|
35 | - move $VERSION to AnyEvent::MP and AnyEvent::MP only. |
| 10 | |
36 | |
| 11 | 1.2 Thu Oct 1 22:59:35 CEST 2009 |
37 | 1.2 Thu Oct 1 22:59:35 CEST 2009 |
| 12 | - fix a rather big bug where message processing could be |
38 | - fix a rather big bug where message processing could be |
| 13 | inhibited completely. |
39 | inhibited completely. |
| 14 | - grp_mon could not return a guard due to a typo. |
40 | - grp_mon could not return a guard due to a typo. |
