On as side note, I'd still say that stateless means no session id.
Jörn Zaefferer-2 wrote: > > Stateless doesn't equal static. A stateless resource can still serve > completely different content based on the session id. > If a returned resource is looked up anywhere BASED on the information within the session (including session id itself) it wouldn't be stateless. Truly, stateless can be non-static, but then the dynamic part would come from i.e. request parameters (or be randomly generated, whatever). -- View this message in context: http://www.nabble.com/Wicket%2C-url-rewriting-and-shared-resources-browser-caching-tp20508529p23095812.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
