[zeromq-dev] lacks

[Andrew Hume]

thanks.
so this is familiar terrain. but the first sticking point
for me is what mechanism is there for a zeromq socket to
reattach? (for example, i am a SUB recipient and and dynamically,
need to reattach to teh PUB (who has changed underneath).)

	andrew

On Apr 24, 2014, at 2:18 PM, Pieter Hintjens <ph at imatix.com> wrote:

> On Thu, Apr 24, 2014 at 10:46 PM, Andrew Hume <andrew at research.att.com> wrote:
> 
>> can you expand on this a little (or a lot)?
>> One thing we lack in ZeroMQ generally is resilience, supervisor trees and
>> such.
> 
> OK, off-the-cuff expansion:
> 
> It seems a missing piece in our puzzle; how to start message
> processing tasks on demand, and handle their deaths smoothly. I'd
> probably want to use messages to communicate such exits. I think we
> could make this work using green threads, with internal or external
> tasks that eventually plug in with some protocols.
> 
> I'd like e.g. to make a web server that uses such a mechanism to start
> handlers for specific URI paths, track their presence, and where
> handlers can cheaply die if they hit issues.
> 
> I'm no expert in supervisor trees, and haven't used Erlang. This is hypothesis.
> 
> -Pieter
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev


-----------------------
Andrew Hume
949-707-1964 (VO and best)
732-420-0907 (NJ)
andrew at research.att.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20140424/26e31a28/attachment.htm>