Travis DePrato
Travis DePrato
(ping @minrk - don't mean to bug but would appreciate a cursory glance)
Ping @minrk @ellisonbg @Carreau @gnestor @jasongrout Would just love to get some eyes on this. :^)
Is that an absolutely hard requirement? This would be an opt-in kind of thing so if the client doesn't support it if would work exactly the same. I'm also not...
Ah - I didn't look at the ipywidgets example closely. I understand. > Yes, it is a requirement. Comm messages are queued with execution requests. Isn't this just an implementation...
> It is specified in the protocol in that both execution requests and comm messages go through the shell channel, and are therefore processed in order. Hence, any kernel properly...
> It sounds like you may want some sort of new introspection messages - probably on the control channel, like the new debugging messages. It seems to me like this...
> it only processes one message at a time I'm not 100% clear what "it" is referring to (the ZMQ socket, the kernel, something else?), but I don't think this...
Which is to say that, given a router socket "shell" and a dealer socket "frontend", it's valid (from a ZMQ POV and subject to the "as far as I understand"...
**Bump** This is still causing lots of issues. :')
> Sorry I was't really tied into this thread originally. Can I ask why the front-end doesn't buffer sending request 101 to the shell until request 100 has completed? In...