Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.unix.programmer > #632

Re: Linux to windows IPC

Message-ID <evuia8-5h1.ln1@wilbur.25thandClement.com> (permalink)
From William Ahern <william@wilbur.25thandClement.com>
Subject Re: Linux to windows IPC
Newsgroups comp.unix.programmer
References <4dd61697$0$9003$c3e8da3$9b4ff22a@news.astraweb.com>
Date 2011-05-20 13:19 -0700

Show all headers | View raw


Matt Charles <mcharles48@gmail.com> wrote:
> Hi,

> I have a Windows .NET client process that I'm developing that's going to 
> need to communicate with some C code running on a Red Hat linux box. 
> The client will send a text request and receive a text response after 
> some database processing has been carried out, the calls will need to be 
> synchronous.

Synchronous where? Regarding the .NET client or the C "code" on the server?
Synchronous how? Are you talking basic I/O or sychronous in regards to some
overall transactional flow?

Windows and .NET frameworks tend to dictate the use of threads for
concurrency (even "asynchronous" calls are just put onto another thread).
This means that all the different modes of communications are more alike
than not, in terms of low-level I/O implementation details.

Not so in C. In C it's as just common to use threads as non-blocking I/O.
There may be callbacks or the implementation may use a resumable state
machine which falls back to the caller. And mixing and matching methods is
more of a hassle than in .NET, where if a library uses a callback or
delegate you can just block and synchronize on a semaphore triggered by the
callback, or otherwise coax the behavior of the library to suit the
application's overall design.

Point being, what will dictate your choice of methods is probably what is
most convenient for the C, server-side of this equation. Is the server code
using its own event loop, something like libevent, or is it just
multithreaded? Are there ready-made solutions that are easily pluggable into
the overall design of the C code?

> What options do I have?  I can think of a few:

> Raw Sockets
> CGI in a webserver
> SOAP / REST calls
> Some sort of RPC generator / library?
> what others?

> What works well and has good library support to save me reinventing the 
> wheel?

Good library support for the C code? Again, it all depends. freshmeat.net is
a solid place to start looking for a solution.

Back to comp.unix.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Linux to windows  IPC Matt Charles <mcharles48@gmail.com> - 2011-05-20 08:21 +0100
  Re: Linux to windows  IPC Mark <i@dontgetlotsofspamanymore.invalid> - 2011-05-20 10:38 +0100
  Re: Linux to windows  IPC Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-05-20 15:00 +0100
  Re: Linux to windows  IPC William Ahern <william@wilbur.25thandClement.com> - 2011-05-20 13:19 -0700
    Re: Linux to windows  IPC Matt Charles <mcharles48@gmail.com> - 2011-05-21 09:25 +0100
      Re: Linux to windows  IPC Ian Collins <ian-news@hotmail.com> - 2011-05-21 20:34 +1200
      Re: Linux to windows  IPC Rainer Weikusat <rweikusat@mssgmbh.com> - 2011-05-22 21:26 +0100
      Re: Linux to windows  IPC Matt Charles <mcharles48@gmail.com> - 2011-05-23 12:19 +0100
  Re: Linux to windows  IPC john.spooner@gmail.com - 2012-10-25 06:31 -0700

csiph-web