Lists and XML-RPC
Daniel Berlinger
daniel at circumtech.com
Thu Jul 26 22:07:19 PDT 2001
Apologies for responding to my own mail...
I inaccurately described the situation earlier... the server is returning this:
HTTP/1.0 200 OK
Server: Helma XML-RPC 1.0
Connection: close
Content-Type: text/xml
Content-Length: 184328
<?xml version="1.0" encoding="ISO-8859-1"?<
<methodResponse>
<params>
<param>
<value>
<array>
<data>
<value>
<array>
<data>
<value>16831 /images/10c.jpg</value>
etc.
as you can see, this has a nested array, and it is this interior array that is truncated. By borrowing some code from betty.rpc.client, and removing the nested array from the response I was able to see the issue.
I have asked the spec holder to explain why he is nesting the arrays (I can't see why and suspect it is bug on his side...). I suspect he'll correct this.
I'm not sure why the interior array is truncated, but there was obviously some work done on this in the xml coercions in Frontier...maybe there is a bug?
If anyone from userLand wishes to see the XML for their own testing purposes, let me know offlist.
Thanks to those who wrote.
d.
> Hello everyone,
>
> I have an application that returns large lists of things as an array via
> XML-RPC. At the moment it is returning 181k worth of stuff and Frontier
> automagically converts this to a list.
>
> In my testing (on Mac), lists are limited to 256K... so my nice long array is
> truncated.
>
> I'm looking at the spec tonight to find out how many times an array is returned,
> because it might be easier to have the spec owner modify it to return a string
> rather than array and deal with issue that way... but just in case, I was
> wondering whether there was a work around?
>
> Copying and modifying (hacking) betty.rpcClient to grab the "raw" string before
> it is processed by xml.compile is possible, but that is sort of... well, a hack.
>
> Any suggestions would be most appreciated,
>
> Thanks,
>
> d.
>
More information about the Frontier-Users
mailing list