<br><div class="gmail_quote"><div class="gmail_quote">On Wed, Mar 26, 2008 at 2:07 PM, Martijn Faassen <<a href="mailto:faassen@startifact.com" target="_blank">faassen@startifact.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi there,<br>
</blockquote><div>Hi <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Thanks for your idea!<br>
<div><div></div><div></div></div></blockquote><div><br>You're welcome <br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div><br>
On Wed, Mar 26, 2008 at 1:53 PM, Thomas Cordival <<a href="mailto:tuxella@gmail.com" target="_blank">tuxella@gmail.com</a>> wrote:<br>
> I think that Zope could be a great framework to develop WebServices in<br>
> python and then it could be interesting to implement a generic kind of view<br>
> for WebServices that could be the base for SOAP or REST interfaces.<br>
><br>
> From a more practical point of view, the idea would be to create a base<br>
> from which it would be easy to implement interfaces for REST, SOAP, XML-RPC<br>
> or other web services oriented protocols.<br>
><br>
> If this would be accepted as an idea for the GSoC, I would be volunteer to<br>
> address it.<br>
<br>
</div></div>I'm a bit surprised: how do you see this working? SOAP and REST are<br>
extremely different ways of approaching web services. Very much in<br>
brief: SOAP exposes an API to the web, and REST a protocol. Web<br>
services on top of SOAP take a very different shape than web services<br>
that use RESTful patterns. I have trouble envisioning a generic view<br>
that is useful as a base to both. Could you sketch out your ideas in<br>
more detail?<br>
</blockquote></div><div><br>Basically the idea would be to let the user handling resquests at a lower level<br>to replace the URL and HTTP handlers. Then, it would allow developpers to implement<br>wrappers for several protocols without having to go as low as Twisted to implement<br>
high-level protocols.<br><br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
In addition, Zope 3 already has a REST support package, and Grok also<br>
contains (different) REST support. Both Zope 3 and Grok share their<br>
XML-RPC support as well. There is also a 'soap' package that adds SOAP<br>
support to Zope 3, though I'm not sure whether it's being actively<br>
used or maintained (which might show there is little demand for SOAP<br>
support in Zope, but perhaps not).</blockquote></div><div><br>I had a quick look on Grok's support for REST but it doesn't seem very well integrated<br>into Zope (but that's normal since Grok is done over Zope) and there isn't any<br>
official implementation for SOAP in Zope, while XML-RPC is being unused for<br>WebServices in new SOA projects.<br><br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Anyway, my response would be to get a lot more specific. "Web services<br>
of any kind in Zope" is rather broad. In addition, I suspect you<br>
should do more research: your message doesn't seem to show awareness<br>
that we already have support for much of what you'd like to create.</blockquote></div><div><br>If you prefer then it could be more REST-centric and then implement a very complete<br>thing that would allow developers to think their RESTful protocol clearly and distinctly<br>
from the objects implementation.<br>What do you think of that ?<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Regards,<br>
<font color="#888888"><br>
Martijn<br>
</font></blockquote></div><br><br clear="all"><br>-- <br><font color="#888888">Thomas CORDIVAL
</font></div><br><br clear="all"><br>-- <br>Thomas CORDIVAL