From: "James Rutherford" <[EMAIL PROTECTED]> > This is, in my humble opinion, pure evil. How can you consider something > to be an *identifier* if you can't actually guarantee that it identifies > something?
I absolutely agree. But how can you guarantee that it resolves to what it is meant to be identifying if you completely disallow the possibility to reassign it? I was tempted to say that you shouldn't be allowed to delete a file that has an external identifier (or at least that the default implementation shouldn't). As soon as I realised that wouldn't be possible, you have to consider the possibility of reassigning the handle. Remember, that such a reassignment is (or rather should only be used for) altering the resolution of the identifier - which doesn't automatically mean that you are conceptually changing what it identifies. G This email has been scanned by Postini. For more information please visit http://www.postini.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
