• Rikki Cattermole (27/27) Jul 12 2014 Alright so, I've just finished Dakka's[0] exception support.

Rikki Cattermole <alphaglosined gmail.com> writes:

Alright so, I've just finished Dakka's[0] exception support.

Functionality supported:

Local actor references
Remote node connections, using given ip/port
Remote actor calling
On start/stop/error support
Capabilities per node (can this node do x? if not which can do to create 
a reference?)
Seemless integration of both actor references to actors
Singleton (controller classes) actor support per node, works with 
AllActorRefs  for calling them e.g. sequentially, or until a return value.

At this point, I'm entering it into maintenance. What this means is I 
cannot myself expand on its functionality e.g. adding encryption. 
However if anybody wants to, please do.
This is what I need, I've tried to make it as flexible as possible and 
inline with how akka works, but as I'm not the most adapt in it. Please 
feel free on drawing up a wanted feature list.

There will be issues with threading, so if anyone is more skilled at it 
and understands Vibe's workers feel free pointing that out.

For anybody interested, the code itself isn't well documented (I'll get 
back to it when I have time). But the actual overall design should be 
fairly documented. The protocol[2] and life cycle[3] can be found on the 
wiki[1].

[0] https://github.com/rikkimax/dakka
[1] https://github.com/rikkimax/dakka/wiki
[2] https://github.com/rikkimax/dakka/wiki/Protocol
[3] https://github.com/rikkimax/dakka/wiki/LifeCycleOfObjects