First of all, thanks for this c++ library. I am using it with VC++ for win32 development and I must say, it's wonderful!
However I didn't see anything about timeouts on client requests, although I think it's important (the server might not be running (or network failures) when I send the request). Will it be hard to implement?
Could u add an overloaded XmlRpcClient::execute() with a timeout parameter (set to INFINITE by default)??
Another question, I understand that a very simple http server is implemented. Is it multithreaded? is it serializing requests? can you easily handle a dozen of simultaneous connections?
best regards,
bertrand
an xml-rpc enthusiast!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If no server is running at the specified hostname+port address, the connection request will be refused and the client execute will return an error. If the host is known but unreachable or the network goes down after a connection has been established, the default system socket timeout applies.
It is a fairly trivial exercise to set the timeout option for a socket, so I should be able to add that feature. I will post here again when its available.
Chris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regarding the server, the default implementation is single threaded but uses non-blocking IO (so it doesn't get hung up waiting for reads/writes on a slow connection to a client). Although I have no need of a multithreaded server, a couple of people using the library have subclassed the server and/or the dispatch object to implement multithreading.
If you look through the messages on this forum there is some code posted.
If I have time I intend to add multithreading to the server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
First of all, thanks for this c++ library. I am using it with VC++ for win32 development and I must say, it's wonderful!
However I didn't see anything about timeouts on client requests, although I think it's important (the server might not be running (or network failures) when I send the request). Will it be hard to implement?
Could u add an overloaded XmlRpcClient::execute() with a timeout parameter (set to INFINITE by default)??
Another question, I understand that a very simple http server is implemented. Is it multithreaded? is it serializing requests? can you easily handle a dozen of simultaneous connections?
best regards,
bertrand
an xml-rpc enthusiast!
I forgot:
I previously talked about synchronous request calls of course.
but what about asynchronous calls? is it implemented (callback functions)?
thanks,
bertrand
ps: I got trouble opening release 0.6 ZIP package (it says there are errors...). could you check?
You are right, the 0.6 zip archive appears to be corrupted.
I have replaced the corrupt zip file.
If no server is running at the specified hostname+port address, the connection request will be refused and the client execute will return an error. If the host is known but unreachable or the network goes down after a connection has been established, the default system socket timeout applies.
It is a fairly trivial exercise to set the timeout option for a socket, so I should be able to add that feature. I will post here again when its available.
Chris
Regarding the server, the default implementation is single threaded but uses non-blocking IO (so it doesn't get hung up waiting for reads/writes on a slow connection to a client). Although I have no need of a multithreaded server, a couple of people using the library have subclassed the server and/or the dispatch object to implement multithreading.
If you look through the messages on this forum there is some code posted.
If I have time I intend to add multithreading to the server.
thanks a lot for your answers!
all the best,
bertrand