Re: [Zope-dev] posting
--On Donnerstag, 16. Dezember 2004 7:11 Uhr +0300 Kenny Chamber <[EMAIL PROTECTED]> wrote: How long after posting should it take for a message to appear on the list? ..between seconds and eternity. Since email is based on a store-and-forward protocol you can not expect to see your posting within XXX minutes in every case although this is usually the case if all systems (including all affected mail servers) should work fine. -aj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] posting
How long after posting should it take for a message to appear on the list? --- Kenny Chamber http://gem-hs.org/contact.html ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Zope-Coders] Roundtrip-safe DAV
Andreas Jung wrote: Please post your patches to the Zope Collector. This list is not the right place to submit patches since they might get lost. I think it is OK to post the patch here (but on one list), with a comment like, "Does this seem like something which would be accepatable in the core? Is it implemented correctly?" After that discussion, then yes, the collector is the right place to post the (possibly amended) patch. Tres. -- === Tres Seaver[EMAIL PROTECTED] Zope Corporation "Zope Dealers" http://www.zope.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope-Coders] Roundtrip-safe DAV
On Wed, 15 Dec 2004 19:32:08 -0200, Leonardo Rochael Almeida <[EMAIL PROTECTED]> wrote: > Em Qua, 2004-12-15 às 20:53 +0100, Andreas Jung escreveu: > > Please post your patches to the Zope Collector. This list is not the right > > place > > to submit patches since they might get lost. > > Though this (zope-dev) is the right place to discuss them (I suggest we > stop crossposting to zope-coders to avoid duplication). > > I haven't looked at the patches, but I like the idea of limiting the > visibility of DAV items to those that make sense. Sorry for posting the patch to the list. I'll add it to a Zope Collector -- the CMF collector seems most appropriate, yeah? Emiliano ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope-Coders] Roundtrip-safe DAV
Em Qua, 2004-12-15 às 20:53 +0100, Andreas Jung escreveu: > Please post your patches to the Zope Collector. This list is not the right > place > to submit patches since they might get lost. Though this (zope-dev) is the right place to discuss them (I suggest we stop crossposting to zope-coders to avoid duplication). I haven't looked at the patches, but I like the idea of limiting the visibility of DAV items to those that make sense. Cheers, Leo -- Leonardo Rochael Almeida <[EMAIL PROTECTED]> ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Zope-Coders] Roundtrip-safe DAV
Please post your patches to the Zope Collector. This list is not the right place to submit patches since they might get lost. -aj --On Mittwoch, 15. Dezember 2004 20:43 Uhr +0100 Emiliano Heyns <[EMAIL PROTECTED]> wrote: Hello people, I'm currently working with some content editors that would like to keep their current WYSIWYG tools and use them in combination with Zope/Plone, and using the DAV interface seemed like the best approach, and it does indeed mostly work. One of the larger problems we face using this approach is that quite a few products expose objects via DAV that are not roundtrip-safe; getting-then-putting will result in unwanted behaviour in some cases, and for other objects I don't see much value in allowing them to be accessed over DAV (like the contents of acl_users). I wrote the attached monkey patch to address this (be kind, I'm pretty new to Python), and Sidnei da Silva (author of DavPack) suggested I post the patch on these lists to see if there was an interest into this approach. What it does is disable DAV access for non-collection resources in general and then selectively turns it on for some (non-exhaustive) list. Folderish objects are enabled by default but can be turned off. Objects/classes can also disable or enable themselves by explicitly setting __dav_resource__ to 0 or 1. I'm not suggesting this particular list is the correct one. Thoughts? With kind regard, Emiliano Heyns ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Roundtrip-safe DAV
Hello people, I'm currently working with some content editors that would like to keep their current WYSIWYG tools and use them in combination with Zope/Plone, and using the DAV interface seemed like the best approach, and it does indeed mostly work. One of the larger problems we face using this approach is that quite a few products expose objects via DAV that are not roundtrip-safe; getting-then-putting will result in unwanted behaviour in some cases, and for other objects I don't see much value in allowing them to be accessed over DAV (like the contents of acl_users). I wrote the attached monkey patch to address this (be kind, I'm pretty new to Python), and Sidnei da Silva (author of DavPack) suggested I post the patch on these lists to see if there was an interest into this approach. What it does is disable DAV access for non-collection resources in general and then selectively turns it on for some (non-exhaustive) list. Folderish objects are enabled by default but can be turned off. Objects/classes can also disable or enable themselves by explicitly setting __dav_resource__ to 0 or 1. I'm not suggesting this particular list is the correct one. Thoughts? With kind regard, Emiliano Heyns __init__.py Description: Binary data ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: SOAP Support for ZOPE
Florent Guillaume wrote: Richard wrote: On Wed, 15 Dec 2004 06:54 am, Aruna Kathiria wrote: I did some work regarding SOAP support on ZOPE and published this document on zope.org. Is there really no interest in getting SOAP support into the Zope core? I've got a guy working on some Microsoft Word stuff at the moment, and he was dumbfounded when he discovered that Zope doesn't support SOAP. In his words, "everyone supports SOAP". Sigh :) There is probably interest, but it needs motivated people like Aruna and you to push it. Are there any objections to getting Aruna's patches into the 2.8 codebase? I'd be willing to do the work - but note I know practically nothing about SOAP - I just want to be able to use it. One problem is that Aruna's approach introduces dependencies to external modules: fpconst, and a patched SOAPy. If these can be resolved, why not. Because of those dependencies, I think support "in the core" is not feasible. However, I believe that it should be possible to create a product which solves those issues. This product would either need to monkey-patch the publisher (as outlined by John Zinit earlier in the thread) or else register a new kind of server, which could be configured (like the WebDAV source server) to listen on its own port. For an example of such a Product, see "ZServerSSL", http://sandbox.rulemaker.net/ngps/zope/zssl/ Tres. -- === Tres Seaver[EMAIL PROTECTED] Zope Corporation "Zope Dealers" http://www.zope.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SOAP Support for ZOPE
Dario Lopez-Kästen wrote: Richard Jones wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 15 Dec 2004 06:54 am, Aruna Kathiria wrote: I did some work regarding SOAP support on ZOPE and published this document on zope.org. Is there really no interest in getting SOAP support into the Zope core? I've got a guy working on some Microsoft Word stuff at the moment, and he was dumbfounded when he discovered that Zope doesn't support SOAP. In his words, "everyone supports SOAP". Sigh :) Are there any objections to getting Aruna's patches into the 2.8 codebase? I'd be willing to do the work - but note I know practically nothing about SOAP - I just want to be able to use it. I would like to have SOAP support in the Zope core (both z2 and z3). We are probably going to be forced to interface with Java based SOAP enabled software next year, and I for one would feel more comfortable being able to say that Zope supports SOAP out of the box... think "important selling point". Ha! That's because you are located in Microsoftistan. Also known as "Sweden". :P But I agree, it would be nice with SOAP support out of the box. However, that means including several third-party libraries, which either is a bit complicated, or may be hard due to licensing. One possible way is to add a module (similar to the soapByCignex.py module) to the ZPublisher and use "try/except ImportError" to import it. The third party python modules could then be downloaded and installed and the server restarted, to add SOAP support. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SOAP Support for ZOPE
Richard wrote: > On Wed, 15 Dec 2004 06:54 am, Aruna Kathiria wrote: > > I did some work regarding SOAP support on ZOPE and published this > > document on zope.org. > > Is there really no interest in getting SOAP support into the Zope > core? I've got a guy working on some Microsoft Word stuff at the > moment, and he was dumbfounded when he discovered that Zope doesn't > support SOAP. In his words, "everyone supports SOAP". Sigh :) There is probably interest, but it needs motivated people like Aruna and you to push it. > Are there any objections to getting Aruna's patches into the 2.8 > codebase? I'd be willing to do the work - but note I know practically > nothing about SOAP - I just want to be able to use it. One problem is that Aruna's approach introduces dependencies to external modules: fpconst, and a patched SOAPy. If these can be resolved, why not. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Events in the core
Florent Guillaume wrote: [snip] Martijn asked important question: > If we backport Zope 3 events, what package will they live in? > How will this relate to Five? What other packages does this draw in > (zope.interface definitely)? Etc. If we want that to work with Five and Zope 2.7, will there be no way to use the current Zope Interface module ? Will we have to use the Zope 3 one ? Can they be used together in a compatible manner ? I'd strongly recommend against trying to make the Zope Interface module work directly with Zope 3 technology. I've tried, Zope corp tried, and it's rather painful. Five only managed to get off the ground when it was decided to use Zope 3 interfaces in parallel to Zope 2's, and basically just to ignore Zope 2's. Five does include Tres' bridge directive that can turn a Zope 2 interface into a Zope 3 interface from ZCML. Regards, Martijn ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SOAP Support for ZOPE
Richard Jones wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 15 Dec 2004 06:54 am, Aruna Kathiria wrote: I did some work regarding SOAP support on ZOPE and published this document on zope.org. Is there really no interest in getting SOAP support into the Zope core? I've got a guy working on some Microsoft Word stuff at the moment, and he was dumbfounded when he discovered that Zope doesn't support SOAP. In his words, "everyone supports SOAP". Sigh :) Are there any objections to getting Aruna's patches into the 2.8 codebase? I'd be willing to do the work - but note I know practically nothing about SOAP - I just want to be able to use it. I would like to have SOAP support in the Zope core (both z2 and z3). We are probably going to be forced to interface with Java based SOAP enabled software next year, and I for one would feel more comfortable being able to say that Zope supports SOAP out of the box... think "important selling point". /dario -- -- --- Dario Lopez-Kästen, IT Systems & Services Chalmers University of Tech. "...and click? damn, I need to kill -9 Word again..." - b using macosx ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
