Colin Paul Adams wrote:
Abel> There are obvious drawbacks and caveats to this solution,
Abel> one being that the Net overhead is significant, the other
It need not be - if your URL starts with http://localhost/ .
Agreed, and in times where web services become increasingly more
abundant (where any method can reside on any remote or local server)
this may well be the way to go in the long run.
Or better still, is simply a custom URI resolver (for a custon URI
scheme e.g. mytime:?generated-id).
Not agreed ;)
Building a custom URI resolver, though trivial, is processor dependent
and that does away with the original promise of my solution: making it
processor neutral. And if you are about to write a URI resolver, it'll
be just as easy to write a basic extension function that takes one
argument (the random string) and returns the current date time.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--