RE: [Zope-dev] A modest proposal: Replace medusa with Twisted
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, -- 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 with Twisted Subject: [Zope-dev] A modest proposal: Replace medusa with Twisted
Actually, this brings up this idea I had - Zope should replace medusa with Twisted. Why, you ask?
1) Twisted separates transport from protocols, and the event loop it uses is extendable and generic. That means:
- It can run on Jython (using threads, someday with java.nio), and it can be integrated with the Tk and GTK event loops.
- Your protocol doesn't have to worry about the transport - Twisted supports SSL, TCP and unix domain sockets right now, without having to make any change to the protocols.
2) Twisted is designed to run multiple servers and protocols at the same time, and these can be changed at runtime. It already includes pure python support for HTTP, FTP, LDAP, SMTP, POP3, DNS, telnet, AIM TOC, and IRC, all integrated with the main event loop (all have server support except DNS and LDAP). Adding new protocols to Zope is not easy, at the moment.
3) Twisted is being actively developed and extended. medusa less so.
4) Good integration with threads - while event based, twisted has a very nice model for dealing with threaded apps.
5) Twisted has Perspective Broker, an async.ready remote-object protocol that supports caching, object migration, and remote messaging, with integrated authentication and authorization. And it ideologically meshes with the "object publisher" notion in Zope. No, really :)
Twisted already includes a high-level web framework, but Zope probably would not use it, and instead build its own on top of twisted's low-level http support.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
I can speak about this one... The difficult part of getting Zope to work on Java, IMHO, is not the server. Without too terribly much work, I think you could get a servlet in front of Zope (once you've taken care of all of the other things). We've made some progress toward getting Zope running on Java (http://www.phabric.org). The past few weeks, phabric has been on the back burner at Web Elite because of unrelated paying work. There are two main areas of work in getting Zope on top of Java: the C modules and differences between C Python and Jython. We've made quite a bit of progress in both of those areas, but there's still more to be done before Zope will fire up and answer a request. Kevin ----- Original Message ----- From: "Bjorn Stabell" <bjorn@exoweb.net> To: <zope-dev@zope.org> Sent: Wednesday, October 10, 2001 6:53 AM Subject: RE: [Zope-dev] A modest proposal: Replace medusa with Twisted
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, -- 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 with Twisted Subject: [Zope-dev] A modest proposal: Replace medusa with Twisted
Actually, this brings up this idea I had - Zope should replace medusa with Twisted. Why, you ask?
1) Twisted separates transport from protocols, and the event loop it uses is extendable and generic. That means:
- It can run on Jython (using threads, someday with java.nio), and it can be integrated with the Tk and GTK event loops.
- Your protocol doesn't have to worry about the transport - Twisted supports SSL, TCP and unix domain sockets right now, without having to make any change to the protocols.
2) Twisted is designed to run multiple servers and protocols at the same time, and these can be changed at runtime. It already includes pure python support for HTTP, FTP, LDAP, SMTP, POP3, DNS, telnet, AIM TOC, and IRC, all integrated with the main event loop (all have server support except DNS and LDAP). Adding new protocols to Zope is not easy, at the moment.
3) Twisted is being actively developed and extended. medusa less so.
4) Good integration with threads - while event based, twisted has a very nice model for dealing with threaded apps.
5) Twisted has Perspective Broker, an async.ready remote-object protocol that supports caching, object migration, and remote messaging, with integrated authentication and authorization. And it ideologically meshes with the "object publisher" notion in Zope. No, really :)
Twisted already includes a high-level web framework, but Zope probably would not use it, and instead build its own on top of twisted's low-level http support.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
participants (2)
-
Bjorn Stabell -
Kevin Dangoor