ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent-MP/Changes
(Generate patch)

Comparing AnyEvent-MP/Changes (file contents):
Revision 1.111 by root, Mon May 3 14:20:51 2010 UTC vs.
Revision 1.131 by root, Thu Mar 8 21:37:51 2012 UTC

1Revision history for AnyEvent::MP 1Revision history for AnyEvent::MP
2 2
3TODO: testsuite 3TODO: testsuite
4TODO: intro: maybe simple job pool example? 4TODO: intro: maybe simple job pool example?
5TODO: intro: mention watchdog... 5TODO: intro: mention watchdog...
6TODO: maybe disbale warnings by default?
7TODO: listener-scopes (10.0.0.1:4040@vpn) and connect-scopes ("vpn,public")
6 8
7faq: can't se anything 9faq: can't se anything
8faq: all is asynch 10faq: all is asynch
9faq: how to interface to non-perl nodes? 11faq: how to interface to non-perl nodes?
10 12
11TODO: maybe disbale warnings by default? 13TODO: update docs
12TODO: lies sadrak mails 14TODO: switch to AnyEvent::Log
15TODO: check gproto, nproto, on connect
16TODO: maybe switch to md5+sha1+sha256 or so...
17TODO: up_nodes for aemp-trace replace by rpc call?
18TODO: listener-less nodes - not supported anymore
19TODO: eg/*
20TODO: secure node request
21TODO: timeout
22TODO: porting-guide
23TODO: global undocumented compat functions?
242
25 - INCOMPATIBLE CHANGE: the node protocol used by this version is not
26 compatible to versions <2 - you have to upgrade all nodes.
27 - INCOMPATIBLE CHANGE: many APIs have changed, see the section
28 "PORTING FROM VERSION 1" in the AnyEvent::MP manpage for details.
29 - AnyEvent::MP::Global is now optional - only seed nodes autoload it
30 and create a fully-meshed network with each other, normal nodes only
31 have to connect to seed nodes, other connections are on-demand.
32 - new "norc" and "force" options for MP::configure to ignore
33 or override the rc file.
34 - move seed code to Kernel.
35 - fixed small typo in MP::Transport.
36 - fix (unused) provider-kv (version sometimes missing).
37 - reduce the default export list of MP::Kernel.
38 - reduced various random delays to zero, as they
39 are hopefully no longer needed with the new global
40 protocol.
41 - implement a secure mode that can suppress remote code execution
42 requests on a per-node/per-request basis.
43 - do not use GMP for generating alphanumeric strings even when
44 available, use a more tricky algorithm instead.
45 - anonymous node names and remote port names have been shortened
46 considerably.
47 - aemp shell now supports "package" selection and offers an
48 $ECHO port you cna send messages to.
49 - rely on perl rand() instead of using /dev/urandom when available, as
50 hopefully it is random enough.
51 - aemp shell no longer leaks one port per command.
52 - nodenames can contain %-escapes such as %n or %u.
53 - aemp now uses aemp/%n/%u as nodename.
54 - known_nodes is gone, it has little value, use all_nodes as
55 replacement.
56 - lots of small change and improvements.
57 - TRACE now shows the portid on SND.
13 58
591.30 Thu Jun 30 11:30:39 CEST 2011
60 - connection errors at the right time would kill node
61 connections in a bad way (patch by Malcolm Studd).
62
631.29 Fri May 7 20:13:39 CEST 2010
64 - codename "Sadrak".
14 - fix error in callback at AnyEvent/MP/Global.pm line 339 65 - fix error in callback at AnyEvent/MP/Global.pm line 339
15 (found by Sadrak). 66 (found by Sadrak).
16 - listener-less nodes had trouble sending keepalive 67 - listener-less nodes had trouble sending keepalive
17 messages on write timeouts (found by Sadrak). 68 messages on write timeouts (found by Sadrak).
18 - the monitor guard could cause a memleak due 69 - the monitor guard could cause a memleak due
19 to autovivification if a mon was cleared after 70 to autovivification if a mon was cleared after
20 the port was gone (analysed by Sadrak). 71 the port was gone (analysed by Sadrak).
72 - do not overwrite the config file if we couldn't read it
73 for some reason (lesson demonstrated by Sadrak).
21 74
221.28 Thu Apr 1 21:23:54 CEST 2010 751.28 Thu Apr 1 21:23:54 CEST 2010
23 - accepted connections didn't correctly set up the SRCNODE 76 - accepted connections didn't correctly set up the SRCNODE
24 in some cases, leading to intra-node messages (such as monitoring) 77 in some cases, leading to intra-node messages (such as monitoring)
25 to fail silently (great testcase by Sadrak). 78 to fail silently (great testcase by Sadrak).

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines