Brad Clements wrote:
My client's websites serve xml with xslt-pi instructions to web clients. We sniff the client, and if that browser can't support client-side transforms we then perform the transform on the server.
In that case, the URL to be resolved is probably already a network URL. I need to be sure that my resolver gets the first crack at it, because I don't want libxslt making a callback to my web server (possibly by a url that the local process doesn't have access to) and definitely occuring outside the context in which it should occur.
That's a reasonable use-case. I removed the first-shot for the default resolver (and a couple of bugs and crashes). This leaves it to users to decide about the trade-off between document re-use and the full flexibility of dynamic document loading. Although I didn't test it, document re-use should now require some additional user code like URL caching: if the document for that URL was already generated, the default resolver should know about it... XSLT document loaders should now be in a preliminary usable state. I'll write up some doctests for the new code (doc/resolvers.txt). That'll also show me if (and where) there are still bugs. Stefan