|
|
| Author |
Message |
|
| Guest |
 Posted: Wed Oct 07, 2009 3:20 pm |
 |
|
|
Guest
|
Hello -
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)? |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Oct 07, 2009 3:41 pm |
|
|
|
Guest
|
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@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Oct 07, 2009 5:37 pm |
|
|
|
Guest
|
We're still developing our infrastructure, so that's not an issue.
Thanks.
- Jim
Jim Irrer |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
