Re: [seam-dev] Seam website optimizations
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.
Okay, for all of you out there who really want to see an improvement in
sfwk.org (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.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
Attachments:
- attachment.html (text/html — 1.7 KB)