DifferentClientsOneZSS

From the FAQ:

"""For instance, with ZEO you can run different versions of the application server on different machines or ports. You might have a public version that has all the management facilities actually removed from the code to prevent login. Alternatively you could bring up a test version that was running new code, ensure that it works, then roll the changes in process by process."""

When is it safe to have two clients that share the same storage server, but interact with it in different ways? What ways are there for this to be done?

Is the answer just "make sure every client writes to the database in ways that the other clients can handle, or one client will mess up the others", and "make sure every client can understand the database, even if they might be looking for different things when they read"? -karl