Standard request/response API
There's been some discussion recently about separating the interfaces in zope.publisher from the implementations to facilitate other implementations. I think it would be great to standardize request and response APIs. I'd love to see this extend beyond the Zope community. I believe that there have been some moves to try to do this at the WSGI level, although I haven't kept up with the discussion. Speaking for myself, I'd be happy to change my code to comform to a python-standard request API assuming that it had enough in it to adapt it to existing APIs. This might be an excellent project for PyCon. Jim -- Jim Fulton Zope Corporation
Jim Fulton wrote:
Speaking for myself, I'd be happy to change my code to comform to a python-standard request API assuming that it had enough in it to adapt it to existing APIs.
Without having used it myself yet, and without making any claim about it being a Python standard, this makes me think of WebOb by Ian Bicking. It defines request and response implementations around WSGI and has evolved from Paste. -- Thomas
On Mar 2, 2009, at 2:08 PM, Thomas Lotze wrote:
Jim Fulton wrote:
Speaking for myself, I'd be happy to change my code to comform to a python-standard request API assuming that it had enough in it to adapt it to existing APIs.
Without having used it myself yet, and without making any claim about it being a Python standard, this makes me think of WebOb by Ian Bicking. It defines request and response implementations around WSGI and has evolved from Paste.
Right. That's what I was thinking of. I don't know how much traction it's gotten. Jim -- Jim Fulton Zope Corporation
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote:
On Mar 2, 2009, at 2:08 PM, Thomas Lotze wrote:
Jim Fulton wrote:
Speaking for myself, I'd be happy to change my code to comform to a python-standard request API assuming that it had enough in it to adapt it to existing APIs. Without having used it myself yet, and without making any claim about it being a Python standard, this makes me think of WebOb by Ian Bicking. It defines request and response implementations around WSGI and has evolved from Paste.
Right. That's what I was thinking of. I don't know how much traction it's gotten.
Most of tne non-Zope, non-Django frameworks use it. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJrE3w+gerLs4ltQ4RAj9OAKCR13Uchl07Ey13sI5c8w50uZNPHACff6rF 6gf6/0+i/zVf/Qryp2rsRYQ= =fKEj -----END PGP SIGNATURE-----
Hi there, Tres Seaver wrote: [snip]
Right. That's what I was thinking of. I don't know how much traction it's gotten.
Most of tne non-Zope, non-Django frameworks use it.
Ah, sorry, I missed this line of answering when I answered myself. I agree it's very popular. I think we could get out of the request/response business if we wanted to, but we'd need an evolutionary path to get there. Regards, Martijn
Hi there, Jim Fulton wrote:
There's been some discussion recently about separating the interfaces in zope.publisher from the implementations to facilitate other implementations.
I think it would be great to standardize request and response APIs. I'd love to see this extend beyond the Zope community. I believe that there have been some moves to try to do this at the WSGI level, although I haven't kept up with the discussion.
See WebOb for Ian Bicking's effort (who did investigate a lot of these APIs including ours in that effort). WebOb is very widely adopted in the WSGI community already and I see no realistic way for us to make any headway there now that it is established. I believe that Pylons, TurboGears 2, repoze.bfg and restish all use it. WebOb is more than an interface but also an implementation and in that sense is quite a bit like our zope.publisher. Even though it's a specific implementation it's on top of WSGI so people can adopt it easily. I think it would be very interesting to look for ways to make bits of Zope work with WebOb somehow. Regards, Martijn
On Tue, 2009-03-03 at 01:33 +0100, Martijn Faassen wrote:
Hi there,
Jim Fulton wrote:
There's been some discussion recently about separating the interfaces in zope.publisher from the implementations to facilitate other implementations.
I think it would be great to standardize request and response APIs. I'd love to see this extend beyond the Zope community. I believe that there have been some moves to try to do this at the WSGI level, although I haven't kept up with the discussion.
See WebOb for Ian Bicking's effort (who did investigate a lot of these APIs including ours in that effort). WebOb is very widely adopted in the WSGI community already and I see no realistic way for us to make any headway there now that it is established. I believe that Pylons, TurboGears 2, repoze.bfg and restish all use it.
WebOb is more than an interface but also an implementation and in that sense is quite a bit like our zope.publisher. Even though it's a specific implementation it's on top of WSGI so people can adopt it easily. I think it would be very interesting to look for ways to make bits of Zope work with WebOb somehow.
@Martijn: This thread somewhat overlapped with the forming of the steering group. Do you think this should go to the list of open issues? -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
Christian Theune wrote:
On Tue, 2009-03-03 at 01:33 +0100, Martijn Faassen wrote: [a possible role for WebOb in the Zope Framework] @Martijn: This thread somewhat overlapped with the forming of the steering group.
Do you think this should go to the list of open issues?
Yes. I've just documented this, thanks for reminding me. Regards, Martijn
On Mar 1, 2009, at 1:00 PM, Jim Fulton wrote:
There's been some discussion recently about separating the interfaces in zope.publisher from the implementations to facilitate other implementations.
I think it would be great to standardize request and response APIs. I'd love to see this extend beyond the Zope community. I believe that there have been some moves to try to do this at the WSGI level, although I haven't kept up with the discussion.
Speaking for myself, I'd be happy to change my code to comform to a python-standard request API assuming that it had enough in it to adapt it to existing APIs.
This might be an excellent project for PyCon.
Hey. I have some other projects to work on there as well, but I'll be at PyCon, and am interested in helping on this (specifically the WebOb idea already discussed). Gary
participants (6)
-
Christian Theune -
Gary Poster -
Jim Fulton -
Martijn Faassen -
Thomas Lotze -
Tres Seaver