Re: E Distributed Programming Clarification

Thanks for all the information, it's much appreciated.

I do have one more question, however.  I started to look into programming
persistent distributed applications, but there doesn't seem to be much
documentation up yet. Fortunately, in *E in a Walnut* there is a code sample
of a persistent chat program.  Toward the end of the file there is the
following line:

timeMachine.addExit(chatReceiver, "chatReceiver", true)

I did a help(timeMachine) in the interpreter, but there doesn't seem to be
any comment for this method. But it does call makeTransplanter.addExit()
with the same arguments, which in turn calls surgeon.addExit().  I looked up
both these other emakers, but I still can't seem to figure out what's going
on.  What does the addExit method do and how is it relevant accomplishing
persistency in distributed programming?

Thanks again for your help,
Jimmy

_______________________________________________
e-lang mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/e-lang