On Mon, Aug 23, 2010 at 4:56 PM, gonzalo diethelm <[email protected]> wrote:
> Minor thing: I still think it would be great to have the > "tcp://eth0:5555" part defined in a single place, so that you could > refer to those endpoints by their names. It's actually two different endpoints, not one. The basic device model has a frontend and a backend socket. Either can connect and/or bind to multiple endpoints but they'll not be the same ones. > Anyway, here is the part I don't really follow: what does the "type: > zqueue" do, exactly? Why is that necessary? What if I want to create a > new type of device, one that holds many different internal queues? Or > perhaps one that routes data incoming from an inproc socket directly out > onto a PUB socket? It's specified at http://rfc.zeromq.org/spec:3. Can you tell me if that helps or not? - Pieter Hintjens iMatix - www.imatix.com _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
