Re: [Zope-dev] Impact of additional protocols handled by Zope?
Hi, Myroslav Opyr [EMAIL PROTECTED] wrote: Dieter Maurer wrote: There is a European project called GroupZope which will provide integration with IMAP and LDAP. The Nuxeo people may be able to tell more. Are there anyone on this list who can give information about progress and give licensing/availability info? This is a project for which we have already committed resources, but the IMAP part hasn't started. The LDAP client part is designed to interact with directories using configurable schemas, and is being currently worked on. We will have a visible product this summer. It will be released under an Open Source license. Unlike your proposal, they plan to integrate with existing OpenSource protocol servers. I, too, think this is a better idea than to make Zope learn all different protocols itself. What servers OpenLDAP? Cyrus? Jabber? Any info would be helpful. Interaction with IMAP and LDAP servers, yes. Jabber is not in the current plans, even though we're thinking about it. Florent -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 10 http://nuxeo.com mailto:[EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Impact of additional protocols handled by Zope?
Jeff Kowalczyk writes: Jabber, IMAP and LDAP are the ones that come to mind immediately, since you'd be that much closer to having Zope fulfill a role that MS Exchange really doesn't; inexpensive, easily maintained groupware for small organizations that need custom workflow app development. There is a European project called GroupZope which will provide integration with IMAP and LDAP. The Nuxedo people may be able to tell more. Unlike your proposal, they plan to integrate with existing OpenSource protocol servers. I, too, think this is a better idea than to make Zope learn all different protocols itself. Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] 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] Impact of additional protocols handled by Zope?
I'm curious what the impact on overall performance would be if products eventually came into existence that extended Zope to directly handle additional protocols and their data requirements, primarily intended for low-volume workgroup kind of traffic. Jabber, IMAP and LDAP are the ones that come to mind immediately, since you'd be that much closer to having Zope fulfill a role that MS Exchange really doesn't; inexpensive, easily maintained groupware for small organizations that need custom workflow app development. Is it practical to consider that Zope might extend into other protocols this way, and can it be done with modular products, or does integration require deep Zope modifications (beyond adding a few lines to Z2.py?) Just a hypothetical, I guess. FWIW, it would be really cool to see a general, host-a-protocol-here hook for plugin products as Zope3 takes shape, configuration in the ZMI if the product writer goes that far. Something that would define a standard interface for Zope3 events to respond to signals the protocol handler might generate, and vice-versa. ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Impact of additional protocols handled by Zope?
Yeah, this is something I'd be very interested in knowing, too. In fact, this particular ability could make or break a community project I'm going to be developing with Zope in the near future. Do you mean like the pluggable access that ZServer provides? I imagine there would also have to be some kind of pass-through backend storage to the actual service layer (like IMAP, for instance). This is definately something I've been thinking about. Getting my gears turning, Eron On Sun, 2002-03-17 at 16:53, Jeff Kowalczyk wrote: I'm curious what the impact on overall performance would be if products eventually came into existence that extended Zope to directly handle additional protocols and their data requirements, primarily intended for low-volume workgroup kind of traffic. Jabber, IMAP and LDAP are the ones that come to mind immediately, since you'd be that much closer to having Zope fulfill a role that MS Exchange really doesn't; inexpensive, easily maintained groupware for small organizations that need custom workflow app development. Is it practical to consider that Zope might extend into other protocols this way, and can it be done with modular products, or does integration require deep Zope modifications (beyond adding a few lines to Z2.py?) Just a hypothetical, I guess. FWIW, it would be really cool to see a general, host-a-protocol-here hook for plugin products as Zope3 takes shape, configuration in the ZMI if the product writer goes that far. Something that would define a standard interface for Zope3 events to respond to signals the protocol handler might generate, and vice-versa. ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 ) --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail scanned for viruses by Declude Virus] ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Impact of additional protocols handled by Zope?
[Eron] Yeah, this is something I'd be very interested in knowing, too. In fact, this particular ability could make or break a community project I'm going to be developing with Zope in the near future. Do you mean like the pluggable access that ZServer provides? I imagine there would also have to be some kind of pass-through backend storage to the actual service layer (like IMAP, for instance). This is definitely something I've been thinking about. [Eron] Getting my gears turning, Eron My thinking is that the protocol(s) that people might develop would be action-interfaces to Zope objects and methods. The canon example is IMAP, I guess. Someone might finish up something like http://www.zope.org/Members/michel/MyWiki/IMAPServer , and access/create/control Zope objects persisted directly in ZODB, using variations on the classes people already have for the various Zope Email Clients. Add Binari's IMAP Plug-In to the ubiquitous Outlook, and you've got a poor-man's Exchange Server*. To get public folder workflow, you'd need to use CMF (or Openflow), but that should change by the time Zope3 takes shape, workflow will apparently be native to Zope. (Can't wait) Jabber (or IRC, etc.) would be a slightly different use case. Jabber.py's maturation might mean that you could have a small number of users conferences authenticated against Zope's users. The users would use normal Jabber clients, but this should make web-chat interfaces very doable, too. A Zope Jabber protocol server might implement active conversations in session memory, and persist to Zope objects in response to a Jabber command. Jabber's logging idioms produce XML documents in the jabber.org implementation, ours would be Zope objects or whatever was needed by the developer. The back-end would be all Zope's turf. As for LDAP, existing LDAP products connect to external LDAP servers. But wouldn't it be useful if Zope's user database, and other folderish resources could be exposed as LDAP, with Zope as the server? A Dynamic DNS protocol handler could pump authenticated user's IP info into the LDAP tree, and so on. I'm probably getting ahead of myself here, its not like python implementations of these sophisticated protocols grow on trees. But they do seem to get started in the python community from time to time, and if Zope offered an easy way to hook a budding protocol implementation in to a mature application server, there might be a lot of can-do attitude to getting them beyond alpha stage. The key would be if the developer could add/delete/configure protocol products as easily as content products. As I said, It wouldn't take much for Zope to be a great Exchange drop-in replacement in your typical small business. It wouldn't really matter that much if python implementations of these protocols didn't have the scalability of their C-based brethren, lots of small Zopes doing big-server work would be a nice thing to develop against. * Better than Exchange, IMHO, because you'd have to be nuts to deploy Exchange or Small Business Manager in a real small business with no on-site IS Manager to handle backups or Active Directory admin duties. ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
