reference another stack

[Jeanne A. E. DeVoto]

At 12:51 AM -0800 1/10/03, John Cuccio wrote:
>I have a rev program running on one mac. I will call this the server. I have
>another program running on another mac, I will call this remote, that make
>reference calls to a stack on the server.
>
>The remote program I am using the stackfile property to place the name of
>the stack. Every thing works fine. When I add a card on the server mac. If I
>call the stack from the remote it does not see the new card. Unless I
>restart the program on the remote. I know this has something to do with that
>rev loads the stack into memory. But why is this happening. If I makes calls
>from the server mac to the stack it see the updates why doesn't the remote
>see it. The only difference in my code is the location of the stack.

The stack is loaded into memory on the machine you're using it on. The
sequence goes like this:

1) You open the stack on the server, loading it into memory.

2) You open the stack on the remote, loading it into the remote machine's
memory.

3) You add a card on the server. This changes the copy in the server's
memory, but not the copy on disk, and not the copy in the remote's memory.
The server will see the new card, but the remote will not because it's
working with a different copy.

4) You save the stack on the server. This changes the copy on disk, but it
doesn't change the copy in the remote's memory.

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.

--
Jeanne A. E. DeVoto ~ jeanne at runrev.com
Runtime Revolution Limited - The Solution for Software Development
http://www.runrev.com/