Thread: Client server application

If you search response time, Middleware solution is not the most convenient, because the overhead account, a specific protocol for your development, based on binary packages will be most efficient.

Hello and thanks for the reply, you are right when you say that the middleware solution is not the most appropriate, but the question is basically access to the shell or linux client, and to launch a program stored in these to do certain functions requested by the client or directly access this application that we are listening to any port and communicate directly with it ..

Wait, How long have the access server to the client, typically, clients access the server to do certain things, what that is supposed to do client and server? Most likely the answer is yes, but can also be that you end up killing flies with cannon fire, that's why I was wondering what you do, we use a middleware requirement of the job is it?

Hello, I recommend you take a look at a DDS (Data Distribution Service) middleware solution. DDS can be used to communicate bewteen applications written in different languages (including C++) and different operating systems (including Linux). It is a publish-subscribe architecture, but can also be used to meet request-response requirements. It has very low overhead and minimal latencies (typically, under 100 usec), so it might be a good fit for your project.

I have used the "CoreDX DDS" product in the past, and it is easy to pick up and use. It is a commercial product, but I think you can get a free license for college/university work. Certainly you can try it out for free.