[Zope] Connecting to Zope with a Thick Client
elabuschagne at gmsonline.co.za
Wed Oct 15 01:05:23 EDT 2003
Thanks for all the replies. Paul, is you say create a server in Twisted,
do you mean a server in the same sense as ZServer? Luckily coding just
about anything in Python is fun, so the extending of ZServer seems like a
viable option. Wouldn't this be better anyway, or do you think it would be
much more work than creating a server in Twisted?
I'll have a look at ZServer's XML-RPC implementation, maybe I can get some
tips there on adding another protocol.
At 01:52 PM 14/10/2003 -0400, Paul Winkler wrote:
>On Tue, Oct 14, 2003 at 06:38:07PM +0100, Toby Dickenson wrote:
> > On Tuesday 14 October 2003 16:47, Roch? Compaan wrote:
> > > You can also look at ZEO, specifically the zrpc package which uses
> > > Python's asyncore and socket modules.
> > Note that the ZEO protocol currently needs for all clients and the
> server to
> > trust each other; there is no security across the zeo link.
>True. I wouldn't use ZEO directly for the original poster's "fat clients".
>Instead, I would consider building a server, maybe in Twisted, that
>implements the necessary protocol and uses zope's nice features
>like security, acquisition, etc. It would be some work but I suspect this
>approach could be very powerful and pretty clean.
>Alternatively, you could extend ZServer / Medusa to provide your
>protocol of choice, but that doesn't sound like as much fun :-)
>Look! Up in the sky! It's SPOOKY TOFU ORTHOPEDIST!
>(random hero from isometric.spaceninja.com)
>Zope maillist - Zope at zope.org
>** No cross posts or HTML encoding! **
>(Related lists -
> http://mail.zope.org/mailman/listinfo/zope-dev )
More information about the Zope