[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CAP: To delete or not to...



Bruce_Kahn@xxxxxxxxxxxxxxxx wrote:


However no where is there any text dealing with what can be done on entries marked for deletion but not actually removed. As such the essentially go into limbo. This is not good unless you are a storage manufacturer.

You can remove them. Why do you think that you can not?

The possible choices for dealing w/marked for deletion entries is to:

1) Allow some way to restore them to full health (aka "Undelete" them) or

That was covered in my e-mail. What did you think of my comments?

2) Clearly state that they are as good as actually removed, can never be restored and will be actually removed at some point later at the CS discression (its an administration issue now...)

It is up to the CUA to remove them from the CS.

      3.  A "DELETED" state entry is created by sending a "DELETE"
         command with the "OPTION" parameter value set to "MARK".  To
         retrieve any deleted object, simply do a query asking for any
         objects that were stored in the "DELETED" state.

As the new text says the "DELETED" state is if OPTION=MARK is set then the entry is DELETEd. It does not define the state of the entry when the CMD:DELETE is used w/o OPTION=MARK...

Yes it does:

   If a component is to be marked for delete and not physically removed,
   then include the "OPTIONS" parameter with its value set to the "MARK"
   value in order to alter its state to "DELETED".

If MARK is not set - it is physically removed.


--

 Doug Royer                     |   http://INET-Consulting.com
 -------------------------------|-----------------------------
 Doug@xxxxxxxxx                 | Office: (208)612-INET
 http://Royer.com/People/Doug   |    Fax: (866)594-8574
                                |   Cell: (208)520-4044

We Do Standards - You Need Standards

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature