reference another stack

[Howard Bornstein]

>If you've saved the stack on the server, then using the "revert" command on
>the remote will reload the stack from the server's disk. This updates the
>copy in the remote's memory so it's the same as the one on the server.

Hi Jeanne,

This raises another question I've been wondering about, since the app I'm 
developing may face this situation.

If a writable stack is placed on a server, is there a way to insure that 
changes made to it by multiple people simulataneously are all kept?

>From your description, if two people are simulataneously writing to the 
stack, probably only one of their changes will be saved (the last person 
to save the stack back--the previous person might have saved their 
changes but it would be overwriten by the last save). What kind of 
strategy could one use to insure that any changes made to the stack 
appear on the server, even if someone else is using the stack at the same 
moment?

Regards,

Howard Bornstein
____________________
D E S I G N  E Q
www.designeq.com