Bug #7300
GMN does not lock PID after DELETE
0%
Description
Apparently, the GMN does not lock the PID after a DELETE call is issued against a PID. The PID should no longer be usable after its associated content is removed from the service. Per Dave: "delete() should remove the bytes, but effectively reserve the identifier so that it can not be reused".
The DELETE operation in GMN needs to be investigated to see if PID locking is implemented, but failed to work, or if PID locking is not yet implemented.
History
#1 Updated by Mark Servilla about 8 years ago
- Assignee changed from Mark Flynn to Roger Dahl
#2 Updated by Roger Dahl about 8 years ago
- Status changed from New to Rejected
After discussion with Dave, we have decided that it's not necessary for MNs to lock deleted PIDs. CNs do lock deleted PIDs, so any reuse of PIDs on a MN will be handled much like conflicts with PIDs used on other MNs. It is recommended that the CNCore.reserveIdentifier() and/or CNCore.generateIdentifier() APIs are used for new PIDs, which will prevent any attempted reuse of deleted PIDs.
