[zeromq-dev] Clean shutdown of malamute client zactor in python binding?

[Aaron Sokoloski]

On 4 February 2016 at 05:45, Arnaud Loonstra <arnaud at sphaero.org> wrote:

> As long as it is in Python it will be sequential anyway. In a real
> concurrent setup you probably want n:1 topology in between the
> webservers and the malamute instance and pass messages, right?
>

Well, yes, but this is a bit of an uncommon type of web server.  Internal
use only, so not many clients, but pretty heavy weight processing.  I'm
trying to avoid having lots of copies of the malamute client, because it
needs to cache some pretty big state.  So instead the process will have a
single client, and webserver threads will query the cache using inproc
sockets or something like that.

By the way, I think python isn't 100% sequential -- execution of python
code is, due to the GIL, but c library code can actually execute in
parallel.

I might not have the same problem if using something like gevent or
eventlet, but making czmq work with one of them is much more work than I
can afford to get into right now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20160204/e7c7ede5/attachment.htm>