Thanks! I'll try that one too to find the easiest solution. For
portability, it is easier to use a new transport class and not have to
patch files of the Python distribution.
Using a similar strategy, I used this class just before I read about
your patch, which works fine too:
http://mail.pytho
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
Hi Andy,
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 is easier to ex
Arno Stienen wrote:
> I'll now try this to fool the client into thinking the server 'should'
> keep the connection open:
>
> http://www.velocityreviews.com/forums/t329401-re-xmlrpc-httplib-and-ssl-http-11-xmlrpc-client.html
>
Just to conclude. Above actually worked and solved my problems with
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
Tijs wrote:
>> Arno Stienen wrote:
>>> Perhaps I should be a bit more specific. When using this code to connect
>>> to a remote XML-RPC server (C++, xmlrpc++0.7 library):
>>>
>>>import xmlrpclib
>>>server = xmlrpclib.Server("http://10.10.101.62:29500";)
>>>print
Tijs,
Thank you very much for specific comments. They are most useful, and
I'll try both strategies. If the latter works out, I'll post the results
back on the list.
Bye,
Arno.
Tijs wrote:
> Arno Stienen wrote:
>
>> Arno Stienen wrote:
>>> Perhaps I should be a bit more specific. When using
Arno Stienen wrote:
> Arno Stienen wrote:
>> Perhaps I should be a bit more specific. When using this code to connect
>> to a remote XML-RPC server (C++, xmlrpc++0.7 library):
>>
>>import xmlrpclib
>>server = xmlrpclib.Server("http://10.10.101.62:29500";)
>>pri
I'm sorry to keep bumping my request, but I've been working on this
problem for several months now and am stuck. Perhaps you do not have a
direct answer, but know someone or someforum where I could ask these
XML-RPC or TCP/IP package questions.
Thanks,
Arno.
Arno Stienen wrote:
> Perhaps I sho
Perhaps I should be a bit more specific. When using this code to connect
to a remote XML-RPC server (C++, xmlrpc++0.7 library):
import xmlrpclib
server = xmlrpclib.Server("http://10.10.101.62:29500";)
print server.Connection_Request("roberto")
the Python command
12 matches
Mail list logo
