Yep, as far as I can tell the asset service does not let the browser cache files and as a result your tapestry apps are probably sending a lot more data than you need to if you are using a lot of assets. I don't know if this has been fixed in later versions but I suspect someone will want to if it hasn't = ). There are some other optimizations you could make to the asset service as well. I don't use the asset service much but I modeled my own file services after it so I have a local fix on my machine for these services. When I get around to it I will help someone patch the asset service itself if they can't figure it out, its not hard to do. -Kris
Kris Rasmussen <[EMAIL PROTECTED]> wrote: Correct me if i am wrong, but the asset service as is does not appear to be respecting the fact that the files have not been modified since the last refresh and as a result they are sent ever browse to the page. I am working on a fix locally but I would suggest that you look into this if it is the case as it could significantly reduce the bandwidth of a tapestry app as well as the cpu time on the server. I am going to verify this and post a fix if anyone is interested. I am using 3.02. Kris __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------- Discover Yahoo! Get on-the-go sports scores, stock quotes, news & more. Check it out!
