| 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: listener-scopes (10.0.0.1:4040@vpn) and connect-scopes ("vpn,public") |
| 6 | |
8 | |
| 7 | faq: can't se anything |
9 | faq: can't se anything |
| 8 | faq: all is asynch |
10 | faq: all is asynch |
| 9 | faq: how to interface to non-perl nodes? |
11 | faq: how to interface to non-perl nodes? |
| 10 | |
12 | |
| 11 | TODO: maybe disbale warnings by default? |
13 | TODO: check gproto, nproto, on connect |
| 12 | TODO: lies sadrak mails |
14 | TODO: eg/* |
|
|
15 | TODO: #TODO##d# markers |
|
|
16 | TODO: limiting reconnecting speed when unreachable? |
|
|
17 | 2 |
|
|
18 | - INCOMPATIBLE CHANGE: the node protocol used by this version is not |
|
|
19 | compatible to versions <2 - you have to upgrade all nodes. |
|
|
20 | - INCOMPATIBLE CHANGE: many APIs have changed, see the section |
|
|
21 | "PORTING FROM VERSION 1" in the AnyEvent::MP manpage for details. |
|
|
22 | - AnyEvent::MP::Global is now optional - only seed nodes autoload it |
|
|
23 | and create a fully-meshed network with each other, normal nodes only |
|
|
24 | have to connect to seed nodes, other connections are on-demand. |
|
|
25 | - new "norc" and "force" options for MP::configure to ignore |
|
|
26 | or override the rc file. |
|
|
27 | - move seed code to Kernel. |
|
|
28 | - non-json receive framing was probably broken. |
|
|
29 | - fixed small typo in MP::Transport. |
|
|
30 | - fix (unused) provider-kv (version sometimes missing). |
|
|
31 | - reduce the default export list of MP::Kernel. |
|
|
32 | - reduced various random delays to zero, as they |
|
|
33 | are hopefully no longer needed with the new global |
|
|
34 | protocol. |
|
|
35 | - implement a secure mode that can suppress code execution |
|
|
36 | requests on a per-node/per-request basis. |
|
|
37 | - do not use GMP for generating alphanumeric strings even when |
|
|
38 | available, use a more tricky algorithm instead. |
|
|
39 | - anonymous node names and remote port names have been shortened |
|
|
40 | considerably. |
|
|
41 | - $AnyEvent::MP::Kernel::SRCNODE contains the node ID of the origin |
|
|
42 | node during message receives. |
|
|
43 | - aemp shell now supports "package" selection and offers an |
|
|
44 | $ECHO port you can send messages to. |
|
|
45 | - rely on perl rand() instead of using /dev/urandom when available, as |
|
|
46 | hopefully it is random enough. |
|
|
47 | - aemp shell no longer leaks one port per command. |
|
|
48 | - nodenames can contain %-escapes such as %n or %u. |
|
|
49 | - aemp now uses aemp/%n/%u as nodename. |
|
|
50 | - configure supports "eval", a small perl snippet to initialsie a node, |
|
|
51 | most useful in "aemp run eval ...". |
|
|
52 | - known_nodes is gone, it has little value, use all_nodes as |
|
|
53 | replacement. |
|
|
54 | - lots of small change and improvements. |
|
|
55 | - node_is_known has been removed. |
|
|
56 | - TRACE now shows the portid on SND. |
|
|
57 | - aggressively reduce number of external modules, to reduce |
|
|
58 | memory usage for nodes. |
|
|
59 | - rework most of the documentation. |
|
|
60 | - clean up MP::Kernel exports. |
| 13 | |
61 | |
|
|
62 | 1.30 Thu Jun 30 11:30:39 CEST 2011 |
|
|
63 | - connection errors at the right time would kill node |
|
|
64 | connections in a bad way (patch by Malcolm Studd). |
|
|
65 | |
|
|
66 | 1.29 Fri May 7 20:13:39 CEST 2010 |
|
|
67 | - codename "Sadrak". |
|
|
68 | - fix error in callback at AnyEvent/MP/Global.pm line 339 |
|
|
69 | (found by Sadrak). |
| 14 | - listener-less nodes had trouble sending keepalive |
70 | - listener-less nodes had trouble sending keepalive |
| 15 | messages on write timeouts (found by Sadrak). |
71 | messages on write timeouts (found by Sadrak). |
| 16 | - the monitor guard could cause a memleak due |
72 | - the monitor guard could cause a memleak due |
| 17 | to autovivification if a mon was cleared after |
73 | to autovivification if a mon was cleared after |
| 18 | the port was gone (analysed by Sadrak). |
74 | the port was gone (analysed by Sadrak). |
|
|
75 | - do not overwrite the config file if we couldn't read it |
|
|
76 | for some reason (lesson demonstrated by Sadrak). |
| 19 | |
77 | |
| 20 | 1.28 Thu Apr 1 21:23:54 CEST 2010 |
78 | 1.28 Thu Apr 1 21:23:54 CEST 2010 |
| 21 | - accepted conenctions didn't corretcly set up the SRCNODE |
79 | - accepted connections didn't correctly set up the SRCNODE |
| 22 | in some cases, leading to intra-node messages (such as monitoring) |
80 | in some cases, leading to intra-node messages (such as monitoring) |
| 23 | to fail silently (great testcase by Sadrak). |
81 | to fail silently (great testcase by Sadrak). |
| 24 | |
82 | |
| 25 | 1.27 Sat Mar 20 21:11:16 CET 2010 |
83 | 1.27 Sat Mar 20 21:11:16 CET 2010 |
| 26 | - avoid exceptions in the transport code if the connection |
84 | - avoid exceptions in the transport code if the connection |
