Eelco Hillenius wrote:
I can see your point with those URLs, but I don't agree with it. You
either have public, stable url's which constitute idempotent actions,
or you have session specific urls, in which you shouldn't even
consider caching imo.
But... in case you don't agree, you might want to delve deeper into
Wicket and e.g. work with your own IRequestTarget/
IRequestTargetResolverStrategy.
I disagree about session-specific URLs being uncachable. I should be
able to reload a page without having to reload all its resources. Adding
jsessionid to the URL works, does it not? So what's the downside?
I took a quick look at IRequestTarget and
IRequestTargetResolverStrategy but they seem to deal with handling
incoming requests, not having anything to do with serving unique
resource URLs to begin with. What did you have in mind?
Thanks,
Gili
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
