Story #8964

[SDKs] Design more idiomatic and convenient Go SDK

Added by Tom Clegg over 1 year ago. Updated 6 months ago.

Status:In ProgressStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:SDKs
Target version:-
Story points-
Velocity based estimate-
ReleaseRFCs

Description

Sketches of client code

(TBD)

Packages (which features go where)

(TBD)

Specific features

(TBD)


Related issues

Related to Arvados - Story #9374: [Crunch2] [SDKs] Refactor duplicate code from crunch-disp... Resolved 06/08/2016

History

#1 Updated by Tom Clegg over 1 year ago

  • Description updated (diff)
  • Category set to SDKs
Some wish-list items:
  • stub API server (for testing client code without bringing up a real server)
  • stub Keep server
  • use more stdlib interfaces like Reader and Writer
  • create new client from env vars
  • create new client from config file
  • thread safety (and clear docs about which things are thread-safe)
  • configurable logging
  • no globals (should be able to run tests in parallel -- except, where necessary, "run test server"-like integration tests that rely on external state)
  • convenient event listener that automatically reconnects after failures (without missing any events) and offers a "timestamp of most recent message" function to test freshness

#2 Updated by Tom Clegg over 1 year ago

TBD: the existing SDK uses map[string]string for request bodies, so you can do things like "update 'state' attribute to 'Running', without touching other attributes". When we use real types for arvados database records, though, we send all attributes with every update request, which can result in unnecessary lost updates. A better way to avoid lost updates is to use Etag and If-Matches. This would have to be implemented on both the client side and the API side.

#3 Updated by Peter Amstutz 6 months ago

  • Status changed from New to In Progress

Also available in: Atom PDF