On Oct 30, 2007, at 1:09 AM, Mattias Jiderhamn wrote: > >> If you sent multiple JMS messages to some target which would >> collect them and wait for a commit, you'd still need to create a >> session to hold all the pending messages, which would be exactly >> the same issue as you have with Hessian. >> > I don't *have* to send multiple messages. I could send a single > message with all the data, since I have it all ready from the > beginning. The main reason I was looking at Hessian and multiple > requests, was to avoid reading all the binary data into memory, but > rather just "stream" it from disk, over HTTP, and down on disk on > the other side.
Ah. That's a totally different situation. I didn't understand. Currently with Hessian, you'd use an InputStream as the final argument to your method. Hessian will read the InputStream and send chunks as the application provides data. On the client side, your InputStream reader will read chunks of data. So you don't need to have the binary data completely in memory at all. I have been thinking of adding javax.activation.DataSource capability to Hessian. It's easy to handle on the sending side, but I'm not sure how to handle it properly on the receiving side. -- Scott > > /Mattias > _______________________________________________ > hessian-interest mailing list > [email protected] > http://maillist.caucho.com/mailman/listinfo/hessian-interest _______________________________________________ hessian-interest mailing list [email protected] http://maillist.caucho.com/mailman/listinfo/hessian-interest
