Doug wrote:
> Furthermore, if we look at the service interface for TAP it will
> probably have a number of operations such as the following:
>
> query data
> query metadata (various, TBD)
> stageData (async operations, TBD)
> getCapabilities
> state-of-health
Is it correct that all these services apart from the stageData ones are intended to be purely synchronous?
If so, why not implement these services using pure HTTP-GET calls? Or is that what you actually mean by REST in this case?
In terms of results delivery, are we expecting results to come back directly to the querying client a la simple conesearch?
Cheers,
Kona.
-- Kona Andrews kea-at-roe.ac.uk AstroGrid Project http://www.astrogrid.org IfA, Royal Observatory, Blackford Hill, Edinburgh EH9 3HJReceived on 2006-10-31Z16:12:35