| 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: $::x = db_mon "'l", sub { use Data::Dump; ddx \@_ } - restart atha, 4 updates |
| 12 | TODO: lies sadrak mails |
14 | TODO: update docs |
|
|
15 | TODO: switch to AnyEvent::Log |
|
|
16 | TODO: Global loaded on demand only, adds grp database and node address database |
|
|
17 | TODO: transport connects use any global node to find addresses (maybe itself) |
|
|
18 | TODO: maybe check g_proto version, if sent? how about node protocol? |
|
|
19 | TODO: connect instantly in node->connect, not with timer-0 |
|
|
20 | TODO: maybe switch to md5+sha1+sha256 or so... |
|
|
21 | TODO: up_nodes for aemp-trace replace by rpc call? |
|
|
22 | 2 |
|
|
23 | - INCOMPATIBLE CHANGE: the node protocol used by this version is not |
|
|
24 | compatible to versions <2 - you have to upgrade all nodes. |
|
|
25 | - INCOMPATIBLE CHANGE: many APIs have changed, see the section |
|
|
26 | "PORTING FROM VERSION 1" in the AnyEvent::MP manpage for details. |
|
|
27 | - AnyEvent::MP::Global is now optional - only seed nodes autoload it |
|
|
28 | and create a fully-meshed network with each other, normal nodes only |
|
|
29 | have to connect to seed nodes, other connections are on-demand. |
|
|
30 | - new "norc" and "force" options for MP::configure to ignore |
|
|
31 | or override the rc file. |
|
|
32 | - move seed code to Kernel. |
|
|
33 | - fixed small typo in MP::Transport. |
|
|
34 | - fix (unused) provider-kv (version sometimes missing). |
|
|
35 | - reduce the default export list of MP::Kernel. |
|
|
36 | - reduced various random delays to zero, as they |
|
|
37 | are hopefully no longer needed with the new global |
|
|
38 | protocol. |
|
|
39 | - implement a secure mode that can suppress remote code execution |
|
|
40 | requests on a per-node/per-request basis. |
|
|
41 | - do not use GMP for generating alphanumeric strings even when |
|
|
42 | available, use a more tricky algorithm instead. |
|
|
43 | - anonymous node names and remote port names have been shortened |
|
|
44 | considerably. |
|
|
45 | - aemp shell now supports "package" selection and offers an |
|
|
46 | $ECHO port you cna send messages to. |
|
|
47 | - rely on perl rand() instead of using /dev/urandom when available, as |
|
|
48 | hopefully it is random enough. |
|
|
49 | - aemp shell no longer leaks one port per command. |
|
|
50 | - nodenames can contain %-escapes such as %n or %u. |
|
|
51 | - aemp now uses aemp/%n/%u as nodename. |
|
|
52 | - known_nodes is gone, it has little value, use all_nodes as |
|
|
53 | replacement. |
|
|
54 | - lots of small change and improvements. |
| 13 | |
55 | |
|
|
56 | 1.30 Thu Jun 30 11:30:39 CEST 2011 |
|
|
57 | - connection errors at the right time would kill node |
|
|
58 | connections in a bad way (patch by Malcolm Studd). |
|
|
59 | |
|
|
60 | 1.29 Fri May 7 20:13:39 CEST 2010 |
|
|
61 | - codename "Sadrak". |
| 14 | - fix error in callback at AnyEvent/MP/Global.pm line 339 |
62 | - fix error in callback at AnyEvent/MP/Global.pm line 339 |
| 15 | (found by Sadrak). |
63 | (found by Sadrak). |
| 16 | - listener-less nodes had trouble sending keepalive |
64 | - listener-less nodes had trouble sending keepalive |
| 17 | messages on write timeouts (found by Sadrak). |
65 | messages on write timeouts (found by Sadrak). |
| 18 | - the monitor guard could cause a memleak due |
66 | - the monitor guard could cause a memleak due |
