[zeromq-dev] RFC:5/ZDCF work

Wes Young wes at barely3am.com
Thu Feb 9 15:42:50 CET 2012

aye, I did some more digging between v2 and v3.1, found those bits (and more around why zloop is the way it is). The project i'm writing sorta has a low level C requirement (for perf reasons), and what I need was a way to configure the sockets sort of on the fly (type, addresses, TLS information … that I need to build in, etc..).

shouldn't be hard to do and contribute back, wanted to make sure it wasn't already done / not done for a specific reason. Sounds like the high level languages sort of took care of the basics, diminishing the need (that and most other stuff is easy to take care of at the high language level).

will mock something up using libconfig and post back, see if we can figure out where it should go.

On Feb 9, 2012, at 8:48 AM, Ian Barber wrote:

> They're just not packed in zeromq - they're not gone conceptually, and in fact many of the bindings ship with device code built in (including more complex ones, I believe python has a monitored queue for example). I don't believe that there has been anything further on this project - most simple devices tend to map to the basic repeater, and more complex ones have been bespoke thus far. Project still has merit though, so feel free to contribute something if you do write some code around it!


More information about the zeromq-dev mailing list