4 ms·
Well, many systems do IPC and often this is done over sockets. Maybe a better question is, in 2018 why don't we have much better, cleaner, simple, IPC? If the
by sonnyblarney 8y ago
Well, many systems do IPC and often this is done over sockets.
Maybe a better question is, in 2018 why don't we have much better, cleaner, simple, IPC?
If the system was slow due to this, it might have been the sheer quantity of data over the IPC/Socket. Looks like they were rendering on one side (i.e. 'making the picture') and then pushing that to a different process to rasterize, i.e. 'draw it on screen' which just seems a little crazy. I'd imagine this was probably due to some kind of legacy thing.
- sinisterdeath 8y agoI think a common approach for IPC these days is to use named pipes. Chromium uses it and I've used it in one of my projects. You still have to deal with serialization and deserialization overhead but its usually pretty quick. https://www.chromium.org/developers/design-documents/inter-process-communication https://www.chromium.org/developers/design-documents/inter-p...
- sonnyblarney 8y agoFunny you should bring that up as I'm just looking into that on Node.JS - how was your experience using pipes? Any warning signs / pot holes?