On Fri, 17 Jun 2011 08:00:25 -0300, Christian Zulehner
<christian.zuleh...@porscheinformatik.at> wrote:
Hi all,
Hi!
seems that the StackAssetRequestHandler always sends back the Assetstack
instead of sending a 304 if not changed.
The class itself has no check for the last-modified timestamp, so the
timestamp is always recreated and thus a the asset is always send backt o
client, no matter if the underlying assets have changed or not.
So regarding performance and network traffic, this seems not quite the
optimal solution.
Found a small conversation here in this list about this issue (around 26
May 2010) , but no follow up or bug entry...
Is this behaviour intentional, if yes why? If not, can I open a Jira
issue for that?
If confirmed, I think this deserves a JIRA issue.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
