At 3:54 PM -0700 4/18/06, Dave Wooldridge wrote:
Really? If true, that's certainly a frightening discovery for me. I've always found that storing the GetSaveInfo string of a folderitem in a DB or XML file (Base64-encoded) to always work when retrieved later as long as the user has not moved or deleted the folderitem that it references.
Worked in what way? For retrieving the file, yes, that's perfectly reliable. But do you mean "worked" as in: you then compare it to some other GetSaveInfo, and find that it still matches? That's the piece that I don't think you can depend on.
Is this not the case? Have I just been lucky in that it has always worked for me?
I think so, but it's probably that this would only rarely fail: only when the user has changed what volumes are mounted, or changed the state of file sharing, for example. Most people don't change these things most of the time.
Since we cannot use AbsolutePath for storing folderitem paths for the obvious reasons that have been repeated on this list, and if GetSaveInfo cannot be reliably counted on, how do people store and retrieve folderitem references for later use?
Hang on -- GetSaveInfo CAN be reliably counted on for storing and retrieving FolderItem references. All I'm saying is that you can't count on the GetSaveInfo string to be the same, for the same file, on two different occasions. In such a situation, both would work fine for retrieving the file, even though they don't contain the same bytes.
I hope this clears things up, - Joe -- Joseph J. Strout [EMAIL PROTECTED] _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
