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