[zeromq-dev] multi-part messages

[Andrew Hume]

it has to do with preventing copying.
for example, in a common case of a process getting a message
and prepending something to it and sending it on,
the thought is to do that as two parts in a multipart message.
especially if the latter message is large.

one could also construct a rationalisation to do with messages
being opaque blobs and not parsing inside them
(because each part has its own size).

On Jan 21, 2012, at 6:38 AM, 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?
> 
> Is it something to do with reliability (disconnects in the middle of a big download SUCKS!)?
> 
> --
> john skaller
> skaller at users.sourceforge.net
> 
> 
> 
> 
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev


------------------
Andrew Hume  (best -> Telework) +1 623-551-2845
andrew at research.att.com  (Work) +1 973-236-2014
AT&T Labs - Research; member of USENIX and LOPSA




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120121/3be7223e/attachment.htm>