Hello, Pyro is cool and relatively easy to use. The only thing I didn't like is that one pyro service server is doing one thing at a time(with my tests, I am maybe wrong??). So if you want to 'distribute' for performance reasons, I think pyro doesn't match. Gilles -----Original Message----- From: Cary O'Brien <cobrien@Radix.Net> To: zope@zope.org <zope@zope.org> Date: Tuesday, May 16, 2000 5:05 PM Subject: [Zope] Anyone used Pyro (Python Remote Objects)?

I'm looking at a way to set up a distributed system, distributed for performance and fault-tolerance. I'm pretty sure about using Zope and Python, and I've been looking at Pyro

http://www.xs4all.nl/~irmen/pyro.html

To handle the remote service accesses. So...

1) Has anyone used this with Zope? It seems as if a client-side management interface would be possible, allowing pointey-clickey access to remote services. This is a bit beyond my Zope understanding at the moment.

2) Pyro uses TCP connections to exchange data. Will Zope allow multiple concurrent RPC calls (i.e. one per thread)?

3) Any other options I should look at[1]? I'm mostly interested in wrapping some business logic around the database and putting it on a different machine for performance and security reasons.

-- cary

[1] I know, I know. I'll go back and read the ZEO stuff today!

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )