Project

General

Profile

Actions

Feature #2823

closed

Standardize on Keep locator format

Added by Tim Pierce almost 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Keep
Target version:
-
Story points:
-
Actions #1

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 string
  • Locator.to_s marshals the locator into an ASCII string (Locator.String() in Go)
Actions #2

Updated by Tim Pierce almost 10 years ago

  • Category set to Keep
Actions #3

Updated by Tim Pierce almost 10 years ago

  • Target version set to 2014-08-06 Sprint
Actions #4

Updated by Tom Clegg almost 10 years ago

See Keep locator format wiki page

Actions #5

Updated by Tom Clegg almost 10 years ago

  • Target version deleted (2014-08-06 Sprint)
Actions #6

Updated by Tom Clegg over 9 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF