[zeromq-dev] PGM 2.0.19rc4 updates require code changes in ZMQ2

Steven McCoy steven.mccoy at miru.hk
Mon Jan 4 16:26:53 CET 2010


oof, updated trunk with fix, see if I can update the tags.

-- 
Steve-o

2010/1/4 Pavol Malosek <malosek at fastmq.com>

>  Hello Steven,
>
> 0MQ pgm_sender has transport->can_recv_data set to false, so
> transport->pending_notify is not initialized.
> Any workaround?
>
> malo
>
> ----- Original Message -----
> *From:* Steven McCoy <steven.mccoy at miru.hk>
> *To:* zeromq-dev at lists.zeromq.org
> *Sent:* Monday, January 04, 2010 5:12 AM
> *Subject:* [zeromq-dev] PGM 2.0.19rc4 updates require code changes in ZMQ2
>
> Hi Hi,
>
>   I noticed Malo recently updated to 2.0.18rc3 which missed the rate
> control precision update Martin worked on before.  I ran through all the
> unit and network tests and discovered a few major regressions in
> functionality for certain edge conditions. One of these was the TX thread
> needs to wake a waiting RX thread if it's timeout value is longer than the
> first SPM heartbeat interval (used for flushing stream ends).  I re-use the
> pending event FD that the RX thread currently uses to notify the application
> of receive-state generated events.
>
> For ZMQ this means pgm_sender.[ch]pp and pgm_socket.cpp need to be updated
> with the additional FD retrieved via pgm_transport_get_pending_fd().
>
> --
> Steve-o
>
> ------------------------------
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20100104/1d2a8c5d/attachment.htm>


More information about the zeromq-dev mailing list