Page History

...

• write takes a serialized string representing the ncsa.service.vizier.tspace.ConfigurationEntry object (see below).
• 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 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 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.

ncsa.service.vizier.tspace.ConfigurationEntry

The object stored in the service's data store and which can be retrieved through the read or take ports. A fuller description of the object is found on the ncsa.tools.ogrscript.tspace page.