Arno,
> Your patches solves the problem too. Thanks!
>
> One thing: if I use the unpatched xmlrpclib.py, the printed output of
> xml calls look like:
>
> {'state': 0, 'str': 'Info_RT'}
>
> But if I use your patch, they look like:
>
> state0strInfo_RT
>
> I prefer the former, as it
I think a better fix than the one I posted below is using the
HTTPConnection library, as opposed to the HTTP library from httplib.
A patch can be found below:
--- /sw/lib/python2.5/xmlrpclib.py 2006-11-29 02:46:38.0
+0100
+++ xmlrpclib.py2007-06-15 16:03:17.0 +0200
@@
On Jun 14, 3:10 pm, [EMAIL PROTECTED] wrote:
> Hi,
>
> > 2. The Python implementation ofxmlrpcis not very robust. It just waits for
> > the connection to close. A well-written client (like your Java client)
> > would detect the presence of a Content-Length header and use that.
>
> I'm facing a simi
Hi,
> 2. The Python implementation ofxmlrpcis not very robust. It just waits for
> the connection to close. A well-written client (like your Java client)
> would detect the presence of a Content-Length header and use that.
I'm facing a similar ordeal here. I think the right thing to do would
be t
