Scott Ferguson wrote (2007-10-30 16:35): > On Oct 30, 2007, at 1:09 AM, Mattias Jiderhamn wrote: > >> 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. > Yes, that is what I found so appealing. I don't know any other remoting framework that supports this. My only problem is that the different binary data files must be transferred within the same transaction (that is, the server/receiver should store them all or throw them all away). Hopefully I could get around this using HiveRemoting and plain old HTTP/Resin sessions. Thanks for the tip Jean-Francois Poilpret!
> 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. > (I don't quite see how this relates to my situation) /Mattias
_______________________________________________ hessian-interest mailing list [email protected] http://maillist.caucho.com/mailman/listinfo/hessian-interest
