--- AnyEvent-MP/Changes 2009/09/08 13:46:25 1.60 +++ AnyEvent-MP/Changes 2009/12/30 15:33:08 1.96 @@ -1,19 +1,79 @@ Revision history for AnyEvent::MP -TODO: global protocol fix? -TODO: use seednodes only to broadcast? TODO: testsuite TODO: intro: maybe simple job pool example? TODO: intro: mention watchdog... -TODO: group monitoring -TODO: cal, cal_func -TODO: mon_nodes should init-call for all up nodes -TODO: better autoseeding, timout*(nconnect+1) -TODO: fix the "trying to contatc node under wrogn address" problem. -2009-09-08 03:58:42 <9> trying connect to seed node 10.0.0.18:4040. -2009-09-08 03:58:42 <9> 10.0.0.18:4040 frank already connected, not connecting again. + - INCOMPATIBLE CHANGE: the high-level node protocol changed, + all nodes need to upgrade. + - remote kil's did not work (reported by Eugene Grigoriev). + - documented monitor_timeout, connect_interval, auth_offer, + auth_accept, framing_format, autocork and nodelay options + and make them configurable via bin/aemp. + - some doc updates. + - remote kil's were not synchronous to message sends which affected + nobody, as remote kils were broken. + +1.24 Wed Dec 9 14:59:52 CET 2009 + - codename "the foul egg". + - increased "unmonitored local port died" message level to 2, so + it is displayed by default now. + - generate random seed at configure time, not module loading time, + so fork&configure works as expected. + - decreased "seed"-related message priority in Global from 0 (d'oh) + to 9, as they are not signifcant. + - new experimental module AnyEvent::MP::DataConn to establish + additional data connections between nodes. + - bin/aemp now loads AnyEvent::Watchdog::Util before trying + to call restart. + - bin/aemp setcert didn't properly handle the filename argument. + - removed empty and unused timeout= parameter from protocol greeting. + +1.23 Fri Nov 6 18:46:26 CET 2009 + - listener-less nodes were misinformed by their masters about + the location of new nodes, and therefore didn't connect + properly in all cases. + - messages send during node-up processing could sometimes get lost, + which would hamper global's ability to mesh the network. + - fixed AnyEvent::MP::Global::grp_reg to return a guard also + in scalar context. + - fixed AnyEvent::MP::Kernel::mon_nodes to return a guard also + in scalar context. + - try to improve error reporting when automatically loading + a function - being unable to load a module will now + stop the process and report the error. + +1.22 Sat Oct 17 03:41:47 CEST 2009 + - fix two rcv-bugs: after adding a tagged rcv, the default + callback would not be used or changed anymore (reported + by Felix Antonius Wilhelm Ostmann, with apologies for + taking so long to releae the fix). + - added Coro::MP introduction to AnyEvent::MP::Intro. + - add peval function. + +1.21 Mon Oct 5 21:58:36 CEST 2009 + - always delay kil messages. + - remote monitor requests were never cleaned up (found by + Sadrak and analysed by elmex). + - move $VERSION to AnyEvent::MP and AnyEvent::MP only. + +1.2 Thu Oct 1 22:59:35 CEST 2009 + - fix a rather big bug where message processing could be + inhibited completely. + - grp_mon could not return a guard due to a typo. + - implement primitive aemp shell. + - do not use bound address as listen length (reported by + Felix Antonius Wilhelm Ostman). + - no longer export an undefined "reg" function from AE::MP. + - the mon_guard return value no longer keeps an additional + reference to the passed refs. + +1.1 Fri Sep 11 04:34:03 CEST 2009 + - bumped the transport protocol to version 1 - sorry, but there + were too many bugfixes/changes. + - new function AnyEvent::MP::cal for simple rpc. - renamed AnyEvent::MP::Global functions to grp_reg|get|mon. + - implemented monitoring for Global groups. - removed all userspace time-outs from the transport, instead rely on tcp retransmit timeouts and tcp keepalive. - spawn now delays spawns on the local node artificially, so @@ -30,6 +90,9 @@ - try to backport to 5.8.2, unfortunately, recursive dependencies rely on Module::Build, which fails at 5.8.7, so YMMV. - use a vastly different reseeding strategy. + - use seed nodes to notify nodes about new nodes. + - in the case where a ndoe learns new addresses after it tried + connecting, prefer the new addrseses over the old ones. 1.0 Wed Sep 2 20:40:43 CEST 2009 - randomise more connection times, but reduce delay to 0.2s (seeds)