I have a remote server that handles various different commands, one of which is an event leaking method.
If the event listed 1 or more events listed in the ready queue for the event, then the event freight comes back immediately. If the queue queue is empty, then this method does not return until the end of a few seconds. In this way I have not run any HTTP / socket timeout. The moment an event is available, the method comes back immediately. In this way the client only makes connections to the server only, and the server does not have to make any connection to the client. This incident mechanism works well I am using the boost library to handle qi, event notifications etc.
There is a problem here while the server is holding back to the event fetch method, during that time, I can not issue any other commands in the source code, XmlRpcDispatch.cpp, in the "Tasks" method Seeing, a simple loop that uses blocked calls for "selection". It seems that the management of a method is busy, no other request is processed.
Question: Am I not seeing anything and can handle multiple requests from XmlRpcpp (xmlrpc ++) asynchronous? Does anyone know of a better xmlrpc library for C ++? I do not think there is a component in Boost Library that allows me to issue remote commands? I really do not care about XML or over-HTTP facility do I need to issue (asynchronous) order on any size or form on TCP? I can offer any input.
I also had some problems with XMLRPC, and many people have tested GSOP and XMLRPC ++ like The solution, but in the end I left and wrote the whole HTML + XMLRPC with scratch and (later I swapped to TinyXMM). It was not really a lot of work; I did it myself in a week, started from scratch and many RPC calls were fully implemented.
Given great results, as its name says, with excellent async and a little upper part, with excellent performance, which was important to me very because it Was running in an embedded environment (MIPS).
> Later, and this may be your case, I've changed the XML, and it was also happy. Its APIs, as well as its message containers, are all types of safe (i.e. you send an int and float, and it is never converted into a string, as is the case with XML), and once You hang it, which does not take much longer, its very productive solution. My recommendation: If you can eat XML, go with it +
If you need XML: +
This stuff from scratch actually It's worth it.
Comments
Post a Comment