On 10 September 2011 04:31, Tom Wilberding wrote:
> We have a TCP based application that we would like to migrate to PGM or
> ePGM (it is one way PUB/SUB). My understanding is that the PGM support
> in ZMQ is built atop OpenPGM.
>
> Are there any hardware requirements (switch hardware support) to
Hey Guys,
In case a producer is not ØMQ, I am thinking to consume messages from
the socket myself ( using their proprietary protocol on top of TCP/IP ), and
then resend these messages to ØMQ over "inproc://" => in other words, just
use ØMQ as an in memory queue only.
1. Is that a good i
We have a TCP based application that we would like to migrate to PGM or
ePGM (it is one way PUB/SUB). My understanding is that the PGM support
in ZMQ is built atop OpenPGM.
Are there any hardware requirements (switch hardware support) to run
these protocols. For instance, our network engineer was
Agree with Mikko.
You have another variable of context_t type out of the loop scope.
Besides this request should be deleted.
If you have reasons to create it via new (auto variable seems to be more
natural),
use auto_ptr, a kind of smart pointer or just explicit delete.
09.09.2011, 02:27, "Mikk
