IPC service and gui

[chmichael]

Dear Danijel,
  Do you have any easy example how to implement an IPC (Inter-process communication) between a service and GUI app without using TCP Lowlevel components ?

Thank you

[D.Tkalcec (RTC)]

There are a lot of examples on using RTC remote functions, which is the easiest way you can achieve communication between applications (inter-process, inside LAN or over the Internet).

To get the best performance when both applications are running on the same PC or when all your clients are inside LAN without a Firewall, simply set "useProxy" and "useWinHTTP" properties to FALSE. This way, you will be using TCP/IP over asynchronous WinSock with a thin HTTP layer, which is comparable in performance to using the TCP/IP components directly.

And if you need even faster performance than you could ever get with asynchronous TCP/IP communication, you can use the TRtcMessageClient and TRtcMessageServer components with third-party transports (for example, NexusDB transports) instead of using TRtcHttpClient and TRtcHttpServer components.

Best Regards,
Danijel Tkalcec

[Kevin Powick]

Danijel,

I think he's looking for something outside of TCP/IP, when both the client and the server process are on the same, physical machine.

Named pipes come to mind.  http://en.wikipedia.org/wiki/Named_pipe

[D.Tkalcec (RTC)]

Thank you. I think you are correct and named pipes are probably the fastest way one can get two applications to communicate with one another when both are running on the same PC. And ... if I am not mistaken, NexusDB components include a named pipes transport, which should work in combination with the RTC SDK when using the rtcMessageClient and rtcMessageServer components.

Best Regards,
Danijel Tkalcec

[chmichael]

Well, i was looking TCP/IP for LAN IPC.

Maybe Name Pipes are fast but TCP/IP is more reliable ?

[D.Tkalcec (RTC)]

For communication between PCs (inside LAN or over the Internet), I would recommend using HTTP/S (works over TCP/IP) because it is reliable and allows you to break the LAN barrier and easily access your Server over the Internet, should that be required.

And if you want to use a different transport based on each clients specific requirements, you can also use the TRtcDualDataServerLink component on the Server to embed more than one transport and make your server-side functionality accessible over more than one communications channel (for example use named pipes for local inter-process communication and HTTP/S for LAN and Internet clients). The most important thing here is to use the standard RTC SDK components, which are based on TRtcDataServer/TRtcDataClient descendant components and using HTTP/S instead of using the low-level TCP/IP or UDP stuff.

Best Regards,
Danijel Tkalcec