Re:Bus1: a new Linux interprocess communication proposal
by goalieca on Thursday August 18, 2016 @10:12AM
(#12312581)
Serialisation is its own problem. Should have nothing to do with IPC. Layered architectures out the window in favour of systemd like monoliths.
[ Parent
| on HN ]
Re:Bus1: a new Linux interprocess communication proposal
by naasking on Thursday August 18, 2016 @10:55AM
(#12312929)
> Serialisation is its own problem. Should have nothing to do with IPC.
Yes and no. There's significant utility to standardizing serialization in your IPC layer. IPC consists of exchanging domain-specific messages, so the message types can be specified in a header shared between endpoints, and data gets serialized in a standard format.
The IPC API then simply reduces to sending/receiving data to/from endpoints, like channels in CPS. And ideally it should be higher-order so you can send an endpoint to another endpoint.
So you don't need to standardize the serialization, but then you just get a plethora of incompatible formats.