I think it's a worthwhile goal. In fact, I think a lot of aspects of libzmq which are currently hard-coded should be made more modular. There are two issues: 1) It's a big task, as mentioned, and someone just has to do it. 2) As a big task, it's also a big stability risk. There's a greater potential to introduce bugs than there would be with smaller changes.
On Thu, Feb 13, 2014 at 12:34 PM, Lyle Thompson <[email protected]>wrote: > OK. Thanks for your feedback, Pieter. I think, then, that I will just do > it the simple way. > > Regards, > Lyle > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Pieter Hintjens > Sent: Thursday, February 13, 2014 12:30 AM > To: ZeroMQ development list > Subject: Re: [zeromq-dev] Protocol Plugins > > On Wed, Feb 12, 2014 at 3:05 AM, Lyle Thompson <[email protected]> > wrote: > > > I guess nobody is interested in pluggable protocols. Thanks anyway. > > Making pluggable protocols in the core library is just a very hard thing. > It would require some major redesigns. > > People have added transports, and it's doable. They're not pluggable > though, in the sense we usually mean. > > I built a simple framework for pluggable protocols over inproc bridges, > some years ago: https://github.com/hintjens/vtx. It didn't get much > attention. > > -Pieter > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
