Changes between Version 1 and Version 2 of DeliveryService/UseCases


Ignore:
Timestamp:
10/07/06 16:18:50 (13 years ago)
Author:
spascoe
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeliveryService/UseCases

    v1 v2  
    1 '''Status''': Draft 
    2  
    31= Introduction = 
    42 
     
    1210I anticipate that NDG services will want to use the DeliveryService to 
    1311both expose CSMLInstances already existing on the file system and 
    14 upload CSMLInstances for exposure to other parties.  I therefore 
    15 suggest a 2 layer interface: 
     12upload CSMLInstances for exposure to other parties.  I suggest a 2 layer interface: 
    1613 
    1714 1. DeliveryService-HTTP provides an interface over HTTP (SOAP or ReST?) to high level functions including: 
     
    2017   1. Monitor transfer in progress 
    2118   1. (Maybe) View CSMLDocument of a CSMLInstanceURI 
    22  1. The DeliveryServices provides a customised bbFTP interface providing the standard FTP commands: send, retrieve, list, mkdir 
     19   1. Transfer CSMLInstance to/from another DeliveryService 
     20 1. DeliveryService-bbFTP provides a customised bbFTP interface with the standard FTP commands: send, retrieve, list, mkdir 
    2321 
    2422= Use Cases = 
     
    3129 1. Client contacts NDGSessionManager and retrieves an AttributeCertificate suitable for the DataProvider referenced in the CSMLInstanceURI. 
    3230 1. Client program establishes connection with the DeliveryService-bbFTP server passing it the AttributeCertificate for authentication. 
    33  1. Client retrieves the CSMLDocument describing the CSMLInstance. ('''DISCUSS''': Alternatively the client could retrieve the CSMLInstance document via the DeliveryService-HTTP interface) 
     31 1. Client retrieves the CSMLDocument describing the CSMLInstance using the CSMLInstanceURI. ('''DISCUSS''': Alternatively the client could retrieve the CSMLInstance document via the DeliveryService-HTTP interface) 
    3432 1. Client parses the CSMLDocument to determine data URI(s). 
    3533 1. Client retrieves data referenced by the CSMLDocument. 
     
    5149In this use case a DataProviderAgent is anticipated to be either a tool operated by the user or a service. 
    5250 
     51 1. DataProvider has a CSMLDocument and associated data files on the local file system.  
    5352 1. DataProviderAgent contacts the local NDGSessionManager and retrieves the local (i.e. not mapped) AttributeCertificate. 
    5453 1. DataProviderAgent contacts DeliveryService-HTTP sending the AttributeCertificate as authentication 
     
    5655 
    5756'''DISCUSS''': Does the DataProviderAgent need to be able to specify the CSMLInstanceURI or should the DeliveryService-HTTP specify it. 
     57 
     58== D. CSMLInstance transfered between 2 DataProviders == 
     59 
     60The DeliveryServices of two DataProviders (DS1 and DS2) interact to copy a CSML instance from one to the other. 
     61 
     62 1. User contacts NDGSessionManager and retrieves an AttributeCertificate. 
     63 1. User contacts DS1-HTTP with the AttributeCertificate requesting the retrieval of CSMLInstanceURI from DS2. 
     64 1. DS1-HTTP acts as a DeliveryService client, contacting DS2-bbFTP with the AttributeCertificate. 
     65   1. DS1-HTTP retrieves the CSMLDocument identified by the CSMLInstanceURI from DS2-bbFTP. 
     66   1. DS1-HTTP parses the CSMLDocument for referenced data files. 
     67   1. DS1-HTTP retrieves the datafiles from DS2-bbFTP. 
     68 1. DS1-HTTP binds the copied CSMLDocument to a new CSMLInstanceURI and returns it to the user. 
     69 
     70'''DISCUSS''': Will we potentially need 2 AttributeCertificates in this case (one for each DataProvider)?