-
1. Re: Streaming vs. large messages
clebert.suconic May 7, 2010 2:09 PM (in response to bill.burke)Streaming and large messages are basically the same thing. Any streaming message is sent as a large message.
A message with a regular body is considered a large message only depending on its size.
When you use streaming, the server will send the message in chunks... and a file will be created at the server. (LargeMessage directory).
The only difference between durable and non-durable large messages is the extension they take. If you restart the server, all the large messages are removed (as there is no reference to them on the journal).
When a durable large message is sent, we also add a reference to the journal (with a reference to the external file).
-
2. Re: Streaming vs. large messages
bill.burke May 7, 2010 5:09 PM (in response to clebert.suconic)Thanks Clebert.
I guess I'm better off reading the HTTP InputStream into a byte array then.
-
3. Re: Streaming vs. large messages
clebert.suconic May 7, 2010 5:38 PM (in response to bill.burke)I guess you would be fine on an InputStream.. unless you don't want a large message
-
4. Re: Streaming vs. large messages
clebert.suconic May 7, 2010 6:11 PM (in response to bill.burke)I guess I know what you mean... you have HttpInputStream for stuff that's not going to be large at all?
I guess then you should use a byte array on small messages and streaming only on the messages that are supposed to be large. you probably have the header with the size the message somewhere.