Re: [Zope-dev] Re: SOAP Support for ZOPE

[Lennart Regebro]

Brian Lloyd wrote:
So the suggestion: I think we'd be in a better place if we:
  - Fix the publisher to at least recognize a SOAP request vs.
an xml-rpc request
  - Provide some kind of 'registration hook' so that a Product
can register with the publisher to handle SOAP requests
  - Have the publisher hand off where appropriate to a registered
SOAP handler if installed, else return an HTTP NotImplemented
or similar if there is no SOAP handler
  - Apply the KISS rule: only one product can register to the be
the SOAP handler, and resist turning this into any kind of
grand-unified-pluggable-publisher architecture ;)
This would be minimally disruptive to the Zope core, while enabling
people interested in SOAP to evolve different solutions without
everybody having to buy into a particular approach or implementation
right now.
A little late, but +1 anyway.
--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
___
Zope-Dev maillist  -  Zope-Dev@zope.org
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: SOAP Support for ZOPE

[John Ziniti]

Brian Lloyd wrote:
  - It is a pain to do anything with SOAP because the
publisher has a hard-coded idea that anything xml must
be xml-rpc
This would be minimally disruptive to the Zope core, while enabling
people interested in SOAP to evolve different solutions without
everybody having to buy into a particular approach or implementation
right now.
+1
I think these ideas are great, but wasn't it also you who said,
Unfortunately, though, this misfeature has  been around for a long time
and would break a lot of people if the default were changed.  I think
getting this changed might be met with some amount of resistance.  If
we're voting ;-) I vote for biting the bullet and making the change
today.
John Ziniti
___
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: SOAP Support for ZOPE

[Aruna Kathiria]

Hi Brian:

I discussed with Michel Pelletier and he will help to produce a patch
that exactly implements your proposal that we'll send to you for your
review. Then we'll just provide an outside Product that calls the
registration function.

Thanks a lot for your suggestions...

Aruna Kathiriya

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Brian Lloyd
Sent: Thursday, December 16, 2004 11:14 AM
To: [EMAIL PROTECTED]
Subject: RE: [Zope-dev] Re: SOAP Support for ZOPE

Hi all - having had to implement a monkey patch product before to enable
SOAP, I'd like to make a few observations and a suggestion:

  - It is a pain to do anything with SOAP because the
publisher has a hard-coded idea that anything xml must
be xml-rpc

  - There is currently no easy way around this w/o monkey
patching, which then leaves you vulnerable to future
changes to the publisher

  - Opinions on the state of SOAP support in the Python world
are far from unanimous - I think it would be premature to
put a particular implementation into Zope proper

  - That said, Zope should make it possible for Cignex and
others to provide SOAP support as add-on products without
unreasonable contortions

So the suggestion: I think we'd be in a better place if we:

  - Fix the publisher to at least recognize a SOAP request vs.
an xml-rpc request

  - Provide some kind of 'registration hook' so that a Product
can register with the publisher to handle SOAP requests

  - Have the publisher hand off where appropriate to a registered
SOAP handler if installed, else return an HTTP NotImplemented
or similar if there is no SOAP handler

  - Apply the KISS rule: only one product can register to the be
the SOAP handler, and resist turning this into any kind of
grand-unified-pluggable-publisher architecture ;)

This would be minimally disruptive to the Zope core, while enabling
people interested in SOAP to evolve different solutions without
everybody having to buy into a particular approach or implementation
right now.


Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering   540.361.1716
Zope Corporation   http://www.zope.com


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Behalf Of Tres Seaver
 Sent: Wednesday, December 15, 2004 1:22 PM
 To: [EMAIL PROTECTED]
 Subject: [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 )


___
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 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

[Tres Seaver]

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 )