Hi Thiago, thank you for your answer! I thought that Java/Tomcat wouldn't be optimal to handle large/many file transfers in a web environment (too high cpu usage) and that Apache would handle it better -- correct me, if I'm wrong. I've now implemented the StreamResponse solution you suggested and it works fine. Anyway, I'll see if the performance will be a problem.
For the moment, it works. Thanks again for your support! René On 24.01.2013 13:00, Thiago H de Paula Figueiredo wrote: > On Thu, 24 Jan 2013 09:49:50 -0200, René Bernhardsgrütter > <rene.bernhardsgruet...@gmail.com> wrote: > >> Hi all, > > Hi! > >> in my current project I need to _send_ large files to authorized users. >> The server mustn't execute/display the files, even if it's a index.html. >> The environment will be an Apache2-frontent, via mod_jk to a Tomcat >> instance where Tapestry runs. > > Before trying some non-Tapestry solution, why don't you try having > Tapestry serving these large files for you using a page specific for > that (so you can have your authorization logic there) that returns a > StreamResponse wrapping the files? This way, doing a good > StreamResponde implementation, must probably using a > BufferedInputStream, you can easily avoid loading the whole file in > memory for serving it (actually, you can even control the size of the > buffer. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
