|
|
|
The purpose of the NG/AMS
Client APIs is to facilitate the implementation of client applications.
|
|
|
|
An API in C and Python are
provided. These provides functions/methods to do most the possible
interaction with the NG/AMS Server.
|
|
|
|
Two client applications are
provided, which can be used to interact with the NG/AMS Server.
|
|
|
|
Also an Archive Client is
provided. This provides a simple manner for data providers to archive data
into the NGAS Archive. Latter may be located on a remote location, accessible
via HTTP. Files to be archived must simply be copied into the so-called Archive
Queue (directory) or a link from the file created in that location. When the
file has been successfully archived it it put in the Archive Files Buffer. It
will remain according to a given timeout. Before deleting a file, the Archive
Client sends a CHECKFILE Command to the remote NG/AMS Server to check if the
file is really in the remote archive. If a file could not be archived
successfully, it remains in the Archive Queue.
|
|
|
|
The Archive Client provides
more features, which require a longer explanation.
|