Hello Dieter, thanks for your answer. Dieter Maurer <dieter@handshake.de> writes:
You mean ZEO client instances not ZEO (server) instances, don't you?
Exactly, sorry for having been ambiguous.
Why do you think your ODBC objects should be consistent across ZEO clients? I do not think that it is necessary as all your requests your be independent which means all transactions inside a single request which implied that connections need not to be shared.
The reason why I think about this ZEO scenario is that I thought it was a goal for a ZEO deployment that all ZEO clients behave identical when they respond to the same request. That requires some sort of shared state, which is what ZODB is used for in ZEO, AFAIK. Furthermore such shared state is only useful when the state persist across requests. So I guess my real question should have been: Is it useful/sensible to keep state across request-boundaries within a database adapter in Zope (such state as ODBC-environment, ODBC-connections, ODBC-statements and ODBC-descriptors)? If you don't know ODBC well enough: How do you do it in comparable remote access adapters (for example a CORBA client in Zope or something)? TIA, andreas