Home/ Questions/Q 934973
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T21:05:08+00:00

I have a remote server which handles various different commands, one of which is

  • 0

I have a remote server which handles various different commands, one of which is an event fetching method.

The event fetch returns right away if there is 1 or more events listed in the queue ready for processing. If the event queue is empty, this method does not return until a timeout of a few seconds. This way I don’t run into any HTTP/socket timeouts. The moment an event becomes available, the method returns right away. This way the client only ever makes connections to the server, and the server does not have to make any connections to the client.
This event mechanism works nicely. I’m using the boost library to handle queues, event notifications, etc.

Here’s the problem. While the server is holding back on returning from the event fetch method, during that time, I can’t issue any other commands.
In the source code, XmlRpcDispatch.cpp, I’m seeing in the “work” method, a simple loop that uses a blocking call to “select”.
Seems like while the handling of a method is busy, no other requests are processed.

Question: am I not seeing something and can XmlRpcpp (xmlrpc++) handle multiple requests asynchronously? Does anyone know of a better xmlrpc library for C++? I don’t suppose the Boost library has a component that lets me issue remote commands?
I actually don’t care about the XML or over-HTTP feature. I simply need to issue (asynchronous) commands over TCP in any shape or form?
I look forward to any input anyone might offer.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I had some problems with XMLRPC also, and investigated many solutions like GSoap and XMLRPC++, but in the end I gave up and wrote the whole HTTP+XMLRPC from scratch using Boost.ASIO and TinyXML++ (later I swaped TinyXML to expat). It wasn’t really that much work; I did it myself in about a week, starting from scratch and ending up with many RPC calls fully implemented.

    Boost.ASIO gave great results. It is, as its name says, totally async, and with excellent performance with little overhead, which to me was very important because it was running in an embedded environment (MIPS).

    Later, and this might be your case, I changed XML to Google’s Protocol-buffers, and was even happier. Its API, as well as its message containers, are all type safe (i.e. you send an int and a float, and it never gets converted to string and back, as is the case with XML), and once you get the hang of it, which doesn’t take very long, its very productive solution.

    My recomendation: if you can ditch XML, go with Boost.ASIO + Protobuf
    If you need XML: Boost.ASIO + Expat

    Doing this stuff from scratch is really worth it.

    • 0