[Modeling-users] Consistency among different processes?

[Federico H. <fh...@vi...>]

Modeling's manual seems to imply that it caches objects in memory
indefinitely, and raises a few issues of cache consistency among
EdititingContexts, as well as strategies to work around them.

The workarounds, and even the "to-be-implemented clean solution" of
creating a mechanism for ECs to broadcast changes all seem to assume,
however, that all ECs reside in the same address space (a Zope server,
for instance). This need not be the case, though: Imagine a typical
client-server application that runs in a single address space on the
client machine. If a machine fetches some rows, and then another one
changes them, the first machine will never see the changes? It may even
break them? This doesn't seem like something that can be fixed by
broadcasting...

	Fede