Re: Horde_Rpc with large data

Quoting Ralf Lang <[email protected]>:

> Hallo,
>
> I had some use cases where Horde_Rpc sent or received large data. It  
> seems there is some hard limit in xmlrpc around 8-9 mb of xml data  
> where it simply fails.

Can you provide more detail about this? I.e., any idea what exactly is  
failing, or where? What exactly happens when it fails?

> If I explicitly call jsonrpc instead of the default xmlrpc, I can  
> transmit much mure data as Rpc arguments. However, the return value  
> of jsonrpc seems to be bare Objects, where xmlrpc returns array with  
> the same parameters.
>
> Now I wonder what would be the intended Behaviour of Horde_Rpc if no  
> explicit rpc protocol is given. Should it switch to jsonrpc if the  
> xml is too large for xmlrpc or should it send a meaningful exception?

Not sure how we wouldn't have an explicit protocol? At least in  
current stable, the protocol is chosen based on the Content-Type  
header of the request. If there is no Content-Type header, we default  
to WebDav since rpc.php is the same entry point.


> -- 
> Ralf Lang
> Linux Consultant / Developer
> Tel.: +49-170-6381563
> Mail: [email protected]
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
> -- 
> dev mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: [email protected]



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-- 
dev mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]