Hello Lutz,
I was thinking...using share, pipes and sockets is a way to communicate 
between newlisp sessions..but only regarding selected function/variables..
Is there a way to fully duplicate 1 running newlisp  to another? 
The 'duplication does send all known functions inside 1 newlisp to the
other newlisp session... Actualy 1 big 'cpymem of the running newlisp memory..
There are advantages on this
(1) newlisp is able to do realtime memory backup, so theoreticaly newlisp
      has a failover..
(2) All sessions have 100% the same enviroment, this means that running
     multiple newlisp sessions yuo can update all in 1 command while running.
(3) a memory snapsshot can be taken from a running newlisp session, which
   could be used again on remote newlisp sessions or local running newlisp
   sessions.. 
(4) Owww and not to forget! having a snapshot of a newlisp makes   encapsulated 
binary distribution of newlisp code possible between machines. 
Linking can be done based on a snapshot.
You could ofcaurse make a difference between copying only the functions
and variables and leave the active working memory alown..or copy it all...
In theory this should be possible, seeking all created functions then 'save
those to memory, copy that memory block and dstribute that via .i.e. a net-eval
to all other newlisp sessions where they accept it, reset/or no reset memory and 
update (unconditional) their session with what they received...
Norman.
			
			
									
									memory duplication
memory duplication
-- (define? (Cornflakes))