On Mon, Apr 11, 2011 at 9:12 PM, Jon Dyte <[email protected]> wrote:
>> I think you misunderstood. The idea is to split devices into a separate >> project, not to ditch them. I'd like to point out that splitting non-core stuff off libzmq is valuable in its own right. It is close to impossible to improve layers that are tightly part of core. As separate projects, they become much easier to improve. Examples: C++ API, stand-alone devices, SWAP, zmq_device. I think the freedom to improve these is worth more than the simplicity of getting them in the core library. Question then becomes "how to simplify packaging and installation". I'd suggest, same route as with OpenPGM, allow these extensions to be built along with libzmq to give a single resulting library. It's what I'd like to happen with libzapi, the new C++ binding, and possibly other bindings, as well. It is quite a lot of packaging work but not unreasonable. And we have the framework for it, with the 2.1, 2.2 'distributions'. So my vote is to continue this process of breaking into layers, but with the condition that the packaging makes it all look like one deliverable again. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
