<div class="gmail_quote"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
The Seam resource servlet does not do conditional GET and cache control headers. That is bad for people using @WebRemote, as this JS is downloaded on every page request, over and over. Also, an application like the wiki that uses the Seam resource servlet extensively for delivering plugin CSS/JS/IMGs is suffering from that. I've mentioned this before on this thread and there is a JIRA issue. If someone wants to work on it, contact me so we can coordinate. This has implications for REST integration as well.</blockquote>
<div><br>Okay, for all of you out there who really want to see an improvement in <a href="http://sfwk.org">sfwk.org</a> (and Seam in general), here is your chance to take action. If no one has time to get to it, I might dedicate time to this issue in the near future.<br>
<br>-Dan</div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>