MS> However, they are _applications_ as opposed to 0MQ core which is a MS> _network stack_. Thus I believe the two should not be mixed in a single MS> project.
My question, when I face issues like this, is whether the benefit outweighs the design purity, or if including the outside elements starts me on a slippery slope that I can see derailing a clean design. The functionality is useful, so it will appear somewhere. MS> Packaging devices with core library kind of suggest that those are some MS> kind of "official" devices and discourages the innovation in the area. That certainly can happen, but if you make it clear that they are minimal, intended as a starting point, and provide ideas for how other devices could add value, you can "solve it with language" to some extent. Where people get discouraged is if your devices are built with special knowledge they don't have easy access to, or if yours are so good, and provide enough functionality, that others don't see a need to do more. If devices are removed from the core, where do we begin on the device ecosystem to replace them? -- Gregg _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
