[heavenlyblue]

>> Zproc uses a Server, which is responsible for storing and communicating the state. >> >> This isolates our resource (state), eliminating the need for locks.

So you've just invented a new name for a coordinator process and called it a new fashion in computation?

[TickleSteve]

No, he's reinvented multiprocessing... pickling data structures across multiple processes.

Just without the 'niceties'.

[zbentley]

You're probably right, but see my comment above: not only is MP possibly superior at being a picking/arbitrating server, but it also supports taking advantage of copy-on-write semantics on Unix-ish systems to transfer memory to children at startup in constant time with no pickling/unpickling necessary.

[TickleSteve]

I agree, multiprocessing will be more performant than ZProc, much more thought has gone into it than the simple 0mq wrapper that is ZProc.

[devxpy]

Exactly.

[devxpy]

Great, now just "stating" how things work is equivalent to inventing them!