> Have you worked out a solution to this problem ?. Not having the Database
> URL in the response makes it difficult to code a very thin client (i.e XSLT
You can put the database URL in the XSLT. It means you can't re-use that
exact transformation for all servers, but you can just import the real
stylesheet that does the work into the top level which has the per-server
> knowing where the search was performed. For example if you save a response,
> without adding the URL to the response data, there is no means of knowing
> where the search was performed.
The response will have the XSLT URL in it, which in turn has the database
When trying to do sophisticated things with unsophisticated tools, it's
only to be expected that there will be problems. Thin clients (aka dumb
clients, aka terminally-braindead clients) are thin for a reason.
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Nebmedes: http://nebmedes.o-r-g.org:8000/
I L L U M I N A T I