On Wednesday 02 May 2007 11:07, Doug Tody wrote:
> A single service could support both: queryData for synchronous DM and
> ADQL-based queries, and optionally stageData for asyn/staged execution.
> The client would then either have to guess which to use, or try a
> few smaller synchronous queries first to determine what to do, and
> then resubmit a larger query as a batch job.
I said earlier that I think this is what we need (single step sync and async querying methods). For what it's worth, I think they both need the word query in the name, for the simple reason that this is what people new to the API will look for. For example, when you first learn the JDBC API, you poke around aimlessly until you find the Statement interface and the method:
ResultSet executeQuery(String sql)
That is where you start. Then you learn about Connection and DriverManager (maybe DataSource) and ResultSet... but you grok it when you see that one method signature.
PS-Sure, JDBC is a nightmare of bad design otherwise, but once someone finds that method signature they can proceed from there and get something working quite quickly.
-- Patrick Dowler Tel/Tél: (250) 363-6914 | fax/télécopieur: (250) 363-0045 Canadian Astronomy Data Centre | Centre canadien de donnees astronomiques National Research Council Canada | Conseil national de recherches Canada Government of Canada | Gouvernement du Canada 5071 West Saanich Road | 5071, chemin West Saanich Victoria, BC | Victoria (C.-B.)Received on 2007-05-02Z21:18:06