On 31/05/07, Larry Stone <[EMAIL PROTECTED]> wrote: > ...hmm, it didn't _used_ to care what the path was at all, it would > retrieve the bitstream referenced by the Sequence ID. Now, at > least on the 1.4.1 system I checked, both SID and path have to match. > > But it doesn't have to be implemetned that way. Since Sequence IDs > are the ONLY Bitstream metadata which must be unique within an Item, > the servlet might as well just ignore the path.
I made this change because it was leading to a lot of infinite URL spaces, e.g. because of uploaded PDFs that contained relative links. It also means that URLs with typos could cause the file to fail to work as expected on some platforms, e.g. xxx/bitstream/12.34/56/1/photo.jpge would retrieve the file but because of the '.jpge' the platform wouldn't know what to do with the file, confusing the user. A possible alternative is to 302 to the correct path, or a smarter 404 page which contains a link to the correct path and the containing item. Either way that URL is only 'semi-persistent' -- in 1.0 (and for MIT) we decided not to give Handles to bitstreams (and that URL contains the handle of the item so we can gracefully degrade to the item itself if the bitstream has gone) though that should be a matter for local policy. Rob ------------------------------------------------------------------------- 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
