http://www.infoq.com/articles/etags
What is an "ETag"? The HTTP protocol specification defines an ETag as the "entity value for the requested variant" (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html - Section 14.19.) Another way of saying this is that the ETag is a token that can be associated with web resource. The web resource is typically a web page, but could also be a JSON or XML document. The server is solely responsible for figuring out what the token is and means, and transfers it to the client in the HTTP Response Header. The process looks like this: 1. Client requests a page (A). 2. Server sends back page A, plus an ETag for A. 3. Client renders the page then caches it, along with the ETag. 4. Client requests page A again, passing along the ETag it got back from the server the last time it made the request. 5. Server examines the ETag and determines that the page hasn't changed since last time the client requested it, so sends back a response of 304 (Not Modified) with an empty body. What you guys think about this? :) Is the wicket cache system "etagged" already? []'s!! -- Bruno Borges Summa Technologies Inc. www.summa-tech.com (11) 8565-7739 (11) 3055-2060 (48) 8404-1300
