Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

COSMOSQueryInterfaceInitialDesign

Revision as of 13:20, 4 April 2007 by Joel.hawkins.compuware.com (Talk | contribs) (New page: === Design Requirements === '''Remoteable''' The Query service must be accessible to remote consumers on both java and non-java platforms. '''Introspectable''' The Query service's capabi...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Design Requirements

Remoteable The Query service must be accessible to remote consumers on both java and non-java platforms.

Introspectable The Query service's capabilities must be discoverable at runtime. Mechanisms must be provide to introspect the service in local and remote environments. The Query service must allow consumers to determine the types of queries that may be specified for the service implementation, the return formats of the service supports, and the valid combinations of query and return formats. Additionally, the Query service must provide a mechanism for determining the scope of the data being queried (for example, the set of machines for which a particular query service exposes log data for).

Decoupled from Implementation The Query service API must not specify any particular underyling data store type or query language. The API must be flexible enough to allow adoptors to easily integrate existing data stores, but must be suitable to encourage de-facto standards and/or standard implementations to emerge.

Optimizable The Query service API must not over-specific to the point of precluding optimizations.


High Level Structure

Query Capability

Query Component Type

Query Response Type

Query Assembly

Back to the top