Re: Frontier::Client is going into an infinite loop on reading a long xml, 1.2 Mb

Paul Libbrecht <[email protected]> Fri, 16 Nov 2007 21:37:30 +0100
Newsgroups gmane.text.xml.rpc.specification
Message-ID <[email protected]>
Oh, hold on!

I did not mean the XML-RPC message...
that I do not see doable (since, again, in most cases, most of it is  
loaded in RAM).

I did mean to chunk at the client and server level, in several xml- 
rpc requests.

paul


Le 16 nov. 07 à 17:33, [email protected] a écrit :

>> If you expect such sizes, I suggest you chunk.
>
> But bear in mind that chunking is not legal XML-RPC.  XML-RPC  
> specifies
> HTTP and specifies a content-length header, while HTTP specifies that
> there is no content-length header in a chunked response.  Nonetheless,
> there are many XML-RPC client and server implementations that use a
> variation of XML-RPC that recognizes some form of chunking.
>
> Also, I suspect a chunked response wouldn't circumvent this bug,  
> because
> the client will surely assemble the chunks into a single virtual  
> memory
> buffer anyway, and that buffer may be where the problem is.  Doesn't
> Frontier::Client use the standard HTTP package?  I would doubt the  
> latter
> can be broken by a large HTTP response.



[Non-text portions of this message have been removed]



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xml-rpc/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/xml-rpc/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/