[zeromq-dev] Meaning of: "Pgm-WARNING: peer expired"?

[Steven McCoy]

On 24 October 2010 01:00, Martin Sustrik <sustrik at 250bpm.com> wrote:

> In the future it would be nice if OpenPGM messages (at least some of them)
> were accessible via 0MQ logging system (sys:// transport). The problem I see
> is that there can be at most one loger function per process. That would
> break as soon as there are two 0MQ contexts in a process (say because the
> app is linking with two libraries, each of them using 0MQ). The loger
> function of the first context would be overwritten by the loger function of
> the second context, resulting in second context distributing its messages
> via the first context :(
>
> Any idea how to solve this?
>
>
Each of the options are not great.  Permissions and trace roles would lead
to a per transport callback, interface enumeration callbacks could be suited
to per thread callbacks.  Multiple contexts in the same thread can only be
managed by a singleton inside ØMQ.

-- 
Steve-o
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20101024/a446ed94/attachment.htm>