On Wednesday, November 9, 2011, Martin Sustrik wrote:
> This second solution makes more sense IMHO, but, at the same time, > requires much more work and experimentation to get it done. > "Honey, would you cook me an egg?" "Well, sure, that makes sense, but if you want an egg you probably also want bacon and coffee, and then you'll want bread and freshly-squeezed fruit juice, but since we don't have any oranges, perhaps you should just wait till tomorrow?" I'd suggest focusing on the egg and whether it has to be boiled, scrambled, or fried. It is just an egg, not breakfast. We have two specific problems: 1. Can 0MQ sockets check the type of their 0MQ peers and reject peers with incompatible types? 2. Can this check be done while maintaining interoperability with old code? Note that making a decent breakfast is *also* a good idea, and you know how this is done in AMQP, with a proper protocol / version header. The failure to do that properly doesn't change the fact that socket type validation is a benefit to users. -Pieter
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
