Page History

...

public interface IConfigurationSpace
{
	voidInteger write( String entryXML ) throws Throwable;
        Integer[] writeB( String[] entryXML ) throws Throwable;
	String[] read( String matchXML, int max ) throws Throwable;
	String[] take( String matchXML, int max, long timeout ) throws Throwable;
	String[] takeNB( String matchXML, int max ) throws Throwable;
}

...

• write takes a serialized string representing the ncsa.service.vizier.tspace.ConfigurationEntry object (see below).
• writeB is a batch method which does the same thing as write on multiple entries.
• 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.

...

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.

ncsa.service.vizier.tspace.ConfigurationMatchRequest

...