- From: Roland Gülle <roland@7val.com>
- Date: Tue, 26 Jun 2007 08:54:55 +0200
- To: "Laura Holmes" <holmes@google.com>
- Cc: public-mobileok-checker@w3.org
Hi Laura,
> 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?
Im attatched:
http://docs.google.com/View?docID=w.dgh5r6zs_5cb7gz3&revision=_latest
but not for specific reason - if you want to attach, go for it!
Actually there is no re-request in the XSLT implemented.
The XPath:
<xsl:if test="ancestor::HTTPResponse[1]/following-
sibling::HTTPResponse[1]
and
not(ancestor::HTTPResponse[1]/following-
sibling::HTTPResponse[1]/status[@code = '304'])">
checks the result of the re-request in the moki document, so the
current implementation needs the 'intelligence' to handle re-request
in the moki document generator.
The question to all:
Should be this handled in the moki document generator or should the
XSLT call java code when this is needed?
Cheers,
Roland
Received on Tuesday, 26 June 2007 06:55:16 UTC