Okay, I’ve decided to go with named queues for my IPC. I thought briefly about using sockets but it’s really a bigger PITA than the examples show (I’ve done it before and it was “Oh, yeah, that’s right” pulled up some old code—over a decade—full of pitfalls).
Named queues are simple. You have a path and you open-read/write-close it. Easy peasy. It’s even atomically locked if you are into that.
I tried out a simple example yesterday. Worked perfectly in a teeny amount of code.
Sockets, in comparison are not simple. For a 1:1 connection they are overly complex, have too many failure states… UDP packets can get lost EVEN on the same machine. This isn’t acceptable (even if it happens rarely). TCP can have lag. The only thing faster is shared memory (which is NOT simple to keep from being mangled).
@feloneouscat
They're simple on Python with a decent framework :)
A good framework has event queues and resilience built in. Heck, even CherryPy which is barely a framework.
Not udp tho except for email spam lol