5 ms·
It sounds like a generally good approach for keeping the UI process responsive at all times. I wonder if the serialization cost behind all those IPC calls becom
by fabiospampinato 7y ago
It sounds like a generally good approach for keeping the UI process responsive at all times. I wonder if the serialization cost behind all those IPC calls becomes an issue at some point, especially when passing large structures back and forth, have you found this to be an issue for your use case?
- swiley 7y agoDoesn’t (or didn’t?) X11 work by serializing every drawing operation and doing IPC? That’s been used on very old machines and is very responsive.
- ptx 7y agoThe MIT-SHM shared memory extension was added pretty early on. And nowadays (in GTK etc.) everything is drawn on the client side and sent over as a bitmap. The old-style serialized drawing commands model is only responsive when you have a very simple UI that doesn't do much drawing.
- jlongster 7y agoI haven't noticed an issue - the only alternative would be to block the renderer and do it in the same process. The IPC uses a local domain socket which is very high performance (better than a web socket) so any overhead is quickly made up for with UI responsiveness. There may be specialized cases where it is a problem and you'll have to figure something out.
- codesushi42 7y agoHow do you secure the socket and prevent a malicious process from connecting to it?