On 22/01/2012, at 11:29 AM, Martin Sustrik wrote: > On 21/01/12 14:38, john skaller wrote: >> Why? >> >> I can't see what it does. Since there's no transmission until all the parts >> are collated >> and no reception until all the parts are collated .. what's wrong with the >> client >> doing that and just sending one big message? > > The original reason for introducing multi-part messages was (as Patrick > correctly explains) to allow for requests messages to gather the list of > nodes it have travelled through, so that corresponding reply message can > travel in the opposite direction. > > Unfortunately, this functionality, aside of being used by 0MQ itself, was > exposed to the end users. > > That in turn means that application logic is now often mingled with 0MQ logic > creating a kind of mis-layering problem.
Ouch. > Too late to fix that now though. Not too late for a new binding though. -- john skaller [email protected] _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
