When you say you're writing the client API for a Python object database, do you mean a database that will only hold Python objects, or one that may contain arbitrary data structures, and be accessible from other languages as well?<p>XMPP may be a more efficient protocol than HTTP for stateful, session-oriented communication, but using it as a database client protocol is going to introduce a lot of overhead as compared to, say, using Protocol Buffers, or even the native ZEO Client interface.<p>Is there something about the ZODB/ZEO combination that doesn't work for your application?
Hi kashif. You might find the following useful:<p>Jack Moffit's blog: <a href="http://metajack.im/" rel="nofollow">http://metajack.im/</a>
Twisted words (python) <a href="http://twistedmatrix.com/trac/wiki/TwistedWords" rel="nofollow">http://twistedmatrix.com/trac/wiki/TwistedWords</a>
If the load is significant, you probably want to use ejabberd for the server. If not, there are solid python implementations.
You will be able to use the python xmpp libs for your client side without issue.