logo       

[jsb@xxxxxx: xml-rpc-client response parsing (+patch)]: msg#00054

lisp.scheme.chicken

Subject: [jsb@xxxxxx: xml-rpc-client response parsing (+patch)]

hi,

i've wondered if there's anything i can do for my xml-rpc.egg patch
to be applied to the official version.

the patch fixes the problem mentioned in the email below and
also has support for basic http authentication on the client side.

kind regards,
hans.

----- Forwarded message from Hans Bulfone <jsb@xxxxxx> -----

From: Hans Bulfone <jsb@xxxxxx>
To: chicken-users@xxxxxxxxxx
Subject: [Chicken-users] xml-rpc-client response parsing (+patch)
Date: Fri, 9 Sep 2005 13:37:34 +0200
User-Agent: Mutt/1.5.6+20040907i

hi,

i'm new to this list and also rather new to chicken and scheme in
general.

i've played with the xml-rpc egg recently and wanted to use it against
an xml-rpc server implemented with ruby-on-rails.
i noticed that fault responses from rails cannot be parsed by
xml-rpc-client because the 'faultCode' is returned with type
i4 instead of int (which is expected by xml-rpc-client).
according to the xml-rpc specs, both types are equivalent.

also, the specs say that two structs with the same fields in
different order are the same, so i thought it would be better
to parse the fault struct in a loop.

i have attached a patch that fixes both, i hope you like it :)
it works for me but i've not tested it thoroughly.

thanks for your work on chicken, i really like it!

regards,
hans.

_______________________________________________
Chicken-users mailing list
Chicken-users@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/chicken-users


----- End forwarded message -----

Attachment: xml-rpc.patch
Description: Text document

_______________________________________________
Chicken-users mailing list
Chicken-users@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/chicken-users
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise