[Zope-dev] A modest proposal: Replace medusa with Twisted

[Bjorn Stabell]

I'm just curious, with Twisted in place, how much other work would have
to be done to run Zope in a Java application server?  Just hypothetical.
Would the persistency and pickling stuff work in Jython?

Regards,
--=20
Bjorn

> -----Original Message-----
> From: Itamar Shtull-Trauring [mailto:lists@itamarst.org]
> Posted At: Wednesday, October 10, 2001 18:11
> Posted To: Zope Developer
> Conversation: [Zope-dev] A modest proposal: Replace medusa=20
> with Twisted
> Subject: [Zope-dev] A modest proposal: Replace medusa with Twisted
>=20
>=20
> Actually, this brings up this idea I had - Zope should=20
> replace medusa with=20
> Twisted. Why, you ask?
>=20
> 1) Twisted separates transport from protocols, and the event=20
> loop it uses is=20
>   extendable and generic. That means:
>=20
>    - It can run on Jython (using threads, someday with=20
> java.nio), and it can=20
> be integrated with the Tk and GTK event loops.
>=20
>    - Your protocol doesn't have to worry about the transport=20
> - Twisted=20
> supports SSL, TCP and unix domain sockets right now, without=20
> having to make=20
> any change to the protocols.
>=20
> 2) Twisted is designed to run multiple servers and protocols=20
> at the same=20
> time, and these can be changed at runtime. It already=20
> includes pure python=20
> support for HTTP, FTP, LDAP, SMTP, POP3, DNS, telnet, AIM=20
> TOC, and IRC, all=20
> integrated with the main event loop (all have server support=20
> except DNS and=20
> LDAP). Adding new protocols to Zope is not easy, at the moment.
>=20
> 3) Twisted is being actively developed and extended. medusa less so.
>=20
> 4) Good integration with threads - while event based, twisted=20
> has a very=20
> nice model for dealing with threaded apps.
>=20
> 5) Twisted has Perspective Broker, an async.ready=20
> remote-object protocol=20
> that supports caching, object migration, and remote messaging, with=20
> integrated authentication and authorization. And it=20
> ideologically meshes=20
> with the "object publisher" notion in Zope. No, really :)
>=20
>=20
> Twisted already includes a high-level web framework, but Zope=20
> probably would=20
> not use it, and instead build its own on top of twisted's=20
> low-level http=20
> support.
>=20
>=20
>=20
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -=20
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope )
>=20