[rabbitmq-discuss] big transfers

Jim Irrer irrer at umich.edu
Wed Oct 7 18:36:47 BST 2009

We're still developing our infrastructure, so that's not an issue.


- Jim

Jim Irrer     irrer at umich.edu       (734) 647-4409
University of Michigan Hospital Radiation Oncology
519 W. William St.             Ann Arbor, MI 48103

2009/10/7 Holger Hoffstätte <holger.hoffstaette at googlemail.com>

> Jim Irrer wrote:
> > Someone must have bumped into this problem before, but what is a
> > good strategy for transferring very large buffers (tens or even
> > hundreds of megabytes)?   No matter how the server is configured,
> > a message could be sent that is too large to handle.
> The typical approach is to take the broker out of the critical path and
> only send metadata, i.e. the necessary information for a client to
> retrieve the payload: file path, url, encoding (e.g. compression), size
> (to allow for up front allocation and possibly rejection in case the local
> node is not up for it) etc. so that the consumer can pick up the big
> message by itself.
> This also implies that all clients need to be able to distinguish between
> regular payloads and proxy messages, so adding this late to an
> architecture can be difficult..
> -h
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20091007/cbe42ad0/attachment.htm 

More information about the rabbitmq-discuss mailing list