Project

General

Profile

Task #850

Story #929: modify client-side resolve() implementations to match new architecture

modify R client to call the resolve() on CN to determine data location

Added by Matthew Jones about 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
d1_client_r
Target version:
Start date:
2010-10-07
Due date:
% Done:

100%

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

Description

Currently the R client assumed that it has a MN service endpoint and calls GET on that endpoint directly. Instead, need to have the only known service endpoint be the CN endpoint, and use the resolve() method to find the proper MNs to use for downloading the data and metadata objets.

History

#1 Updated by Matthew Jones about 14 years ago

R client now uses resolve() against the CN to locate the MN for an object, then downloads that object. However, there is some confusion about the format of the resolve() response described in ticket #884. Need to refactor the R client to use the new resolve() response when it is refactored.

#2 Updated by Matthew Jones about 14 years ago

  • Target version deleted (CCI-0.6)
  • Parent task set to #929
  • Milestone set to CCI-0.6

#3 Updated by Dave Vieglais about 14 years ago

  • Tracker changed from Bug to Task
  • Start date set to 2010-10-07

#4 Updated by Matthew Jones about 14 years ago

  • Status changed from New to Closed

Modified R-client to use the new resolve() response syntax as encoded in ObjectLocationList, so now the R client uses the baseUrl for the CN to find the proper location against which resolve() calls should be made. This completes this task, although the R client itself needs significantly more work to generalize it for robustness.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)