Yeah, seems like a pretty serious performance/bandwidth issue. Hopefully people recognize the implications of this. Your patch will definatly work with the newest release (3.0.4) however with the older releases you need to check the server date headers and send 304 not modified responses as appropriate. I'm with you about the 4+ releases. I think there are some nice changes going into them but for those of us who are developing massive apps with older versions switching over to new builds isn't all that easy ;), and definatly not practical until the 4+ releases stabalize. Nevertheless, I don't mind patching my own version in exchange for more time spent on innovating better solutions, I think its worth it. Gotta keep up with and beat the trends ;)... ruby on rails, jsf, new versions of .net, etc... only way tapestry is gonna make it without a massive following behind it just yet. -Kris
Viktor Szathmary <[EMAIL PROTECTED]> wrote: I have implemented and submitted a patch for this a while ago. I hope, that one fine day, it will be applied and a 3.0.4 release will be cut, for those oldschool users out there, who are not all that excited about 4.0 yet, just want to see a few minor tweaks ;) See http://article.gmane.org/gmane.comp.jakarta.tapestry.devel/4981 viktor On 6/12/05, Kris Rasmussen wrote: > 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 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! > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
