I made a small patch to enable the user to pass in the HttpClient they want
the library to use. This was needed for my project because the xmlrpc back
end required a cookie to authenticate the user. This cookie was retrieved
and saved with the HttpClient i setup and then i just pass that to the
library and it authenticated to the xmlrpc server. I figured others might
like the opportunity to pass in their own HttpClient rather then use the one
the library creates for whatever reason. Attached is the patch(I think its
based on an older version but its simple enough to not matter).
Original issue reported on code.google.com by sgay...@gmail.com on 12 Jan 2010 at 5:30
Original issue reported on code.google.com by
sgay...@gmail.com
on 12 Jan 2010 at 5:30Attachments: