I have been using this library for a little while and have found it to be very helpful. I am running an XMLRPC client against a python server on a system running embedded Linux.
We have found that running a client built using the XMLRPC++ library on Linux (compiled with gcc) against our server works with no problem.
The client I wrote and compiled on my Win2000 machine, using the Borland C++ Builder 6 compiler causes a seg fault on the python server.
We have guessed maybe this is due to HTTP 1.0 vs HTTP 1.1, the python server uses HTTP 1.0. Is it possible to switch to use HTTP 1.0 within this library? Or should we convert our server to only use 1.1? I would appreciate any help with this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-11-11
Okay, never mind. We found a python library that uses HTTP 1.1, and is faster anyway than the standard one. Now it works like a charm. Thanks for putting together this library!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been using this library for a little while and have found it to be very helpful. I am running an XMLRPC client against a python server on a system running embedded Linux.
We have found that running a client built using the XMLRPC++ library on Linux (compiled with gcc) against our server works with no problem.
The client I wrote and compiled on my Win2000 machine, using the Borland C++ Builder 6 compiler causes a seg fault on the python server.
We have guessed maybe this is due to HTTP 1.0 vs HTTP 1.1, the python server uses HTTP 1.0. Is it possible to switch to use HTTP 1.0 within this library? Or should we convert our server to only use 1.1? I would appreciate any help with this.
Okay, never mind. We found a python library that uses HTTP 1.1, and is faster anyway than the standard one. Now it works like a charm. Thanks for putting together this library!