- From: Laura Holmes <holmes@google.com>
- Date: Mon, 25 Jun 2007 17:45:47 -0400
- To: public-mobileok-checker@w3.org
- Message-ID: <135a9f560706251445y18e9661bhfdd9bdbf483fff87@mail.gmail.com>
Hey team, As the CachingTest.xsl stands right now, we don't have an implementation for how to re-request the HTTP headers and then test the new results against the old data (the last two tests of 3.2 in Basic Tests). Right now I'm thinking it might be better to have the xsl call to the java code to perform this test. As a pseudo implementation: Take in the old URI and the original value to be tested Append the specified new request headers, then re-request the page Perform the comparisons between the original value and the new value Return a boolean to the xsl as to whether the test passed or failed However, this clashes with the current implementation of the comparison. For example: <xsl:if test="ancestor::HTTPResponse[1]/following-sibling::HTTPResponse[1] and not(ancestor::HTTPResponse[1]/following-sibling::HTTPResponse[1]/status[@code = '304'])"> Is anyone attached to this implementation for any specific reason? And if so, can you explain to me the logic behind the request being implemented prior to this comparison? Thanks, Laura
Received on Monday, 25 June 2007 21:46:05 UTC