←back to thread

112 points zardinality | 1 comments | | HN request time: 0.208s | source
Show context
pjmlp ◴[] No.42195953[source]
> Using a full-featured RPC framework for IPC seems like overkill when the processes run on the same machine.

That is exactly what COM/WinRT, XPC, Android Binder, D-BUS are.

Naturally they have several optimisations for local execution.

replies(4): >>42196335 #>>42197280 #>>42201053 #>>42209092 #
merb ◴[] No.42197280[source]
Btw. Modern windows also superports Unix domain sockets, so if you have an app that has another service that will run on the same machine or on a different one it is not so bad to use grpc over uds.
replies(1): >>42197431 #
pjmlp ◴[] No.42197431[source]
Nice idea, although it is still slower than COM.

COM can run over the network (DCOM), inside the same computer on its own process (out-proc), inside the client (in-proc), designed for in-proc but running as out-proc (COM host).

So for max performance, with the caveat of possibly damaging the host, in-proc will do it, and be faster than any kind of sockets.

replies(3): >>42197698 #>>42202005 #>>42202658 #
1. tgma ◴[] No.42197698[source]
> COM can run over the network (DCOM)

Ah the good ol' Blaster worm...

https://en.wikipedia.org/wiki/Blaster_(computer_worm)