On Friday, 19. September 2003 21:38, Matt Sergeant wrote: > On 19 Sep 2003, at 10:52, Jörg Walter wrote: > > I can easily back out the change in XPathScript, as it is the only > > module not > > working. The others work well even on several of my large sites using > > all > > sorts of file://, sql://, document_root relative and axkit:// URIs from > > within XSLT, XSP and XInclude. Thus I would like to leave the rest in > > place, > > as it is obviously working and at least one of our long-time users > > asked me > > when this feature is going in. > > I think the bigger issue is we haven't really discussed this feature. > Are we sure alternate URI schemes is the best way to do this? What > makes this better than a provider for anything other than axkit://?
Basically, there are two use cases. The one is if you want to include data which you don't want to be available via the web. You'd have to configure an apache subdir with the providers, then put access control into place but see that it doesn't mess with your own retrievals, and finally get stuck as axkit uses either the current style provider or the content provider, not the one configured in the target location. Big trouble to set up and get working. Contrast this to an XMLDB repository, where you would simply retrieve "xmldb://collection/subcollection/document.xml". No setup, just load the module and you are up and running. No accidental external accesses, no provider messup. This is just like "file://" - it isn't strictly neccessary, since you could simply configure apache for the requested location, and yet repeatedly people use that since the other way is much too complicated. Don't confuse this with URLs that contain queries or something - this is a simple, plain document retrieval mechanism, it is not designed to extend URL retrievals into a query mechanism. The second use case is for the case you use the FileWrite provider (or my XMLDB or SQL providers, that are API-compatible). In an XSP page, you usually have to go through several steps to get a provider - if the target doesn't exist yet, it sometimes is even more difficult. Now a simple get_uri()-call is sufficient. Of course, the write-back support being experimental in itself, this isn't as important, but still, there is an advantage. -- CU Joerg PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94
