Project

General

Profile

Task #2809

Story #1906: Review, revise, and update architecture documentation

MNStorage.update() - Make behavior explicit

Added by Roger Dahl over 9 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Documentation
Target version:
Start date:
2012-05-24
Due date:
% Done:

0%

Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:

Description

The current documentation for MNStorage.update() provides a choice for MNs on how to handle update requests that do not contain obsoletes and obsoletedBy fields. The MN can either reject the request, or fill in the missing values. It would be better to specify that MNs MUST fill in the values if they are missing. This would simplify the use case of a simple one to one update. If the fields are specified, they should match the parameters and may, optionally, specify an update that obsoletes multiple objects with a single object.

History

#1 Updated by Dave Vieglais about 7 years ago

  • Target version set to Maintenance Backlog

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)