[zeromq-dev] Automagical zdevice/1.0 now available

gonzalo diethelm gdiethelm at dcv.cl
Mon Aug 23 16:56:37 CEST 2010


>    {
>         "context": {
>             "iothreads": 1,
>             "verbose": true
>         },
>         "main" : {
>             "type": "zqueue",
>             "frontend": {
>                 "option": {
>                     "hwm": 1000,
>                     "swap": 25000000
>                 },
>                 "bind": "tcp://eth0:5555"
>             },
>             "backend": {
>                 "bind": "tcp://eth0:5556"
>             }
>         }
>     }

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.

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?

Perhaps this ties in with the previous comments about 39 threads in a
device, etc.

-- 
Gonzalo Diethelm




More information about the zeromq-dev mailing list