Project

General

Profile

Task #6754

Architecture API loose ends

Added by Rob Nahf almost 7 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Architecture Design
Target version:
Start date:
2015-01-13
Due date:
% Done:

0%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

While comparing v1 to v2 APIs, the following questions came up:

  1. the ping() methods are listed in the table as returning null, but in actuality, we return a Date.
  2. Are we keeping CN.search in the V2 APIs? I thought this one was deprecated.
  3. the systemMetadataChanged method moved from v1.MNAuth to v2.MNRead. Was that intentional? Is it necessary?
  4. synchronizationFailed returns Type.Boolean in the table, instead of a simple boolean that all other methods return. Implementations use simple boolean.

History

#1 Updated by Dave Vieglais almost 7 years ago

Need to update the description of systemMetadataChanged in the MN APIs

#2 Updated by Rob Nahf almost 7 years ago

regarding
* item 2: CN.search - it was decided in standup to deprecate the method, and not include in v2 CN API
* item 3: MN.systemMetadataChanged - it was in v1.MNAuth to allow MNs to receive updated AccessPolicies; in v2, it seems like we only need it to propagate Replica information, so it could move to MN.Replicate API or MN.Storage (or stay in MN.Auth). will move to MN.Replicate

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)