Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Delete Communication uses the general communication pattern with an IdentifyPillarsForDelete and a Delete Primitive. May also include a confirmation, finalisation and Undelete part. To be analysed.
Delete communication starts as the general communication pattern

  • Client sends IdentifyPillarsForDeleteRequest message with data ID, and all pillars in SLA reply with IdentifyPillarsForDeleteReply messages
  • Client sends DeleteRequest messages with data ID and all pillars in SLA reply with DeleteReply messages

It is not currently decided whether data will now be deleted on the specified pillar or on the repository and DeleteComplete messages sent, or do we want a two-phase commit where the data is now in an 'under deletion state' and the client must send a delete confirmation before the pillars finalise the deletion.

See also Undelete under Delete Design Discussions

  • No labels