Actions
Feature #2823
closedStandardize on Keep locator format
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Keep
Target version:
-
Story points:
-
Updated by Tim Pierce almost 10 years ago
- Tracker changed from Bug to Feature
All Arvados components should use a consistent format for Keep locators, and any code that reads or parses locators should recognize any form of a locator (e.g. with size hint, without size hint, with signature, without signature). A component may reject a request if it finds a locator that lacks necessary information (e.g. a missing permission signature), but it should parse them in consistent ways.
A good place to start would be:
[[:xdigit:]]{32}(\+[[:digit:]]+)?(\+A[[:xdigit:]]+@[[:xdigit:]]{8})?
which should match any 32-digit locator with an optional size hint and an optional signature.
Possible API:- define a Locator type with accessor functions
hash
,size
,signature
,timestamp
Locator.parse
parses a locator from a stringLocator.to_s
marshals the locator into an ASCII string (Locator.String()
in Go)
Updated by Tim Pierce almost 10 years ago
- Target version set to 2014-08-06 Sprint
Updated by Tom Clegg almost 10 years ago
- Target version deleted (
2014-08-06 Sprint)
Actions