Page History

...

• write takes a serialized string representing the ncsa.service.vizier.tspace.ConfigurationEntry object (see below); returns the entry id.
• writeB is a batch method which does the same thing as write on multiple entries; returns array of ids corresponding to each entry.
• read and take are batch methods, both requiring a serialized string representing the ncsa.service.vizier.tspace.ConfigurationMatchRequest object (see below), along with an integer indicating the maximum number of tuples entries to return (default is 10; it is advisable not to set this number too high, as Axis will have trouble managing extremely large SOAP packets); the array returned contains serialized ncsa.service.vizier.tspace.ConfigurationEntry objects.
• take also requires a timeout (if set to t <= 0, the non-blocking method is called), whereas takeNB will return immediately subsequent to issuing the request against the data store.
  • takeNB can return null if no tuples entries satisfy the request constraints.
  • take will not return null unless timeout <= 0.
  • take may return an empty array (length 0) if its timeout has been exceeded.

...

• If id is null, the object will be added as a new entry.
• If id is not null, an attempt will be made to update an existing object with that id. The fields subject to update are:
  • timeTaken
  • timeCompleted
  • retried
  • ranOn

See further the ncsa.tools.ogrscript.tspace page.

If the id is set, it is not necessary to provide a complete description of the entry; only the XML elements or attributes corresponding to the 4 updateable fields above will be processed. See further the ncsa.tools.ogrscript.tspace page.

ncsa.service.vizier.tspace.ConfigurationMatchRequest

...