-----Original Message-----
From: Robert Sanderson [mailto:[log in to unmask]]
Sent: 17 March 2004 15:18
To: [log in to unmask]
Subject: Re: Database URL in EchoedRequests


>> 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
>definitions.

This has no impact on saving a response.

>> 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
>URL.
The stylesheet URL isn't always present and sometimes the stylesheet URL is
relative to the Database URI - therefore not an entirely perfect answer to
the problem.

>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.

I know - it's just mildly irritating that the lack of a simple piece of
functionality
prevents them working.

Bill
--
      ,'/:.          Dr Robert Sanderson ([log in to unmask])
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Nebmedes:  http://nebmedes.o-r-g.org:8000/
____/:::::::::::::.
I L L U M I N A T I


**************************************************************************

Experience the British Library online at www.bl.uk

Adopt a Book this season ! Help the British Library conserve the world's
knowledge.  www.bl.uk/adoptabook

*************************************************************************

The information contained in this e-mail is confidential and may be legally
privileged. It is intended for the addressee(s) only. If you are not the
intended recipient, please delete this e-mail and notify the
[log in to unmask] : The contents of this e-mail must not be disclosed or
copied without the sender's consent.

The statements and opinions expressed in this message are those of the
author and do not necessarily reflect those of the British Library. The
British Library does not take any responsibility for the views of the
author.

*************************************************************************