Heh, I'm dealing with a pretty big legacy code base, which at the moment uses cherrypy :( I can only tackle one bit at a time. Thanks for the tip though.
On 4 February 2016 at 07:49, Colin Ingarfield <[email protected]> wrote: > Maybe Tornado would work for what you're trying to do: > http://www.tornadoweb.org/en/stable/ > > It has an asynchronous web server that can be integrated with 0MQ. > > > On 2/4/16 7:41 AM, Aaron Sokoloski wrote: > > On 4 February 2016 at 05:45, Arnaud Loonstra <[email protected]> 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. > > > > > _______________________________________________ > zeromq-dev mailing > [email protected]http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
