-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Theune wrote:
> On Mon, 2009-05-25 at 17:08 +0200, Michael Haubenwallner wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Christian Theune wrote:
>>> [...]
>>>
>>> Nevertheless: passing in 0 seems to be the safe bet in general
On Mon, 2009-05-25 at 17:08 +0200, Michael Haubenwallner wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Christian Theune wrote:
> > [...]
> >
> > Nevertheless: passing in 0 seems to be the safe bet in general and I
> > wonder what is actually breaking. I haven't seen a traceback be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Theune wrote:
> On Wed, 2009-03-18 at 13:12 +0100, Michael Haubenwallner wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Michael Haubenwallner wrote:
>>> When using paste.httpserver instead of twisted.wsgi server
>>> zope.pub
On Wed, 2009-03-18 at 13:12 +0100, Michael Haubenwallner wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Michael Haubenwallner wrote:
> > When using paste.httpserver instead of twisted.wsgi server
> > zope.publisher.xmlrpc.XMLRPCRequest.processInputs() hangs when reading 0
> > Bytes f
Hi Michael
> Betreff: Re: [Zope-dev] XML-RPC does not work under the paster process
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Michael Haubenwallner wrote:
> > When using paste.httpserver instead of twisted.wsgi server
> > zope.publisher.xmlrpc.XMLRP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Haubenwallner wrote:
> When using paste.httpserver instead of twisted.wsgi server
> zope.publisher.xmlrpc.XMLRPCRequest.processInputs() hangs when reading 0
> Bytes from the request (wsgi.input ).
>
> As i found the zope.publisher.http.HTTPInp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When using paste.httpserver instead of twisted.wsgi server
zope.publisher.xmlrpc.XMLRPCRequest.processInputs() hangs when reading 0
Bytes from the request (wsgi.input ).
As i found the zope.publisher.http.HTTPInputStream.readlines() signature
was chan