On Thu, 24 Jan 2013 14:07:31 -0200, René Bernhardsgrütter
<rene.bernhardsgruet...@gmail.com> wrote:
Hi,
Hi!
I wouldn't say that. File transfers are affected by IO, not CPU.
I've read this somewhere several months ago and yesterday again here:
https://blogs.warwick.ac.uk/chrismay/entry/mod_x_sendfile/
I'd like to see how you implemented it.
Basically like the HowTo
[https://wiki.apache.org/tapestry/Tapestry5HowToStreamAnExistingBinaryFile]
but I shortened it a little bit:
Quite simple, no? :)
The only ugly thing for users who want to copy the direct file link was
the event request:
[server]/index.ajaxuploadarea.download/61/nEWEaMExZ5xbJzSmNQQe?t:ac=5tAnW,
where 61 is the fileReferenceId and nEW.. the folderName.
I've now also integrated url rewriting (as
http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/).
Event URLs were never meant to be seen by end users. You can have a way
better URL without URL rewriting by creating a page just for returning the
StreamResponse on its onActivate() method. You'll use PageLink instead of
ActionLink or EventLink. Just put all the info you'll need in the context
parameter.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
