On Wed, Jun 06, 2007 at 10:45:42AM +0100, Graham Triggs wrote:
> 5) Should we include the bitstream id as part of the url, so that we can
> match that instead of the filename (although the name would still be
> included as a hint to the browser)

This has been discussed as part of the (now epic) persistent identifier
discussion, and there seems to be some concern about how the client
interprets the name of the file if it isn't made explicit in the URL.
Basically, it boils down to whether all clients understand the
Content-disposition HTTP header (where we would set the file name), and
if not, whether we care (personally, I don't think it's an issue).

Removing the file name from the URL space would actually solve a few
problems (for a start, the BitstreamServlet would be a lot nicer to look
at), but would have knock-on effects (as already observed) in the case
of HTML content that we (kind of) support inside DSpace. Personally, I'm
not convinced that this is a good idea at all, but it is a feature we
currently support, so we can't abandon it without debate.

cheers,

Jim

-- 
James Rutherford          |  Hewlett-Packard Limited registered Office:
Research Engineer         |  Cain Road,
HP Labs                   |  Bracknell,
Bristol, UK               |  Berks
+44 117 312 7066          |  RG12 1HN.
[EMAIL PROTECTED]   |  Registered No: 690597 England

The contents of this message and any attachments to it are confidential and
may be legally privileged. If you have received this message in error, you
should delete it from your system immediately and advise the sender. To any
recipient of this message within HP, unless otherwise stated you should
consider this message and attachments as "HP CONFIDENTIAL".

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to