Skip Navigation

The Computer Journal 2002 45(2):202-212; doi:10.1093/comjnl/45.2.202
© 2002 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Parimala, N.
Right arrow Search for Related Content
Social Bookmarking
 Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Explicit Operation Specification for Component Databases

N. Parimala1

1 School of Computer and Systems Sciences, Jawaharlal Nehru University, New Delhi 110 067, India Email: parimala_n@hotmail.com

Database queries within a component framework usually take the form of a string passed to an operation in a component's interface. The interface operation accepts a value of type string as an actual parameter and implements the necessary support to resolve the query. In such an approach, a component's interface does not explicitly state the queries supported by that component. In this paper, we present an approach in which queries supported by a component are explicitly defined in its interface enabling a contract between a client of an interface and a component to be agreed. In our approach, a client creates a well-defined context within which interface operations can be executed. A context enables more complex queries to be constructed as sequences of related queries and saved contexts can be further combined to form more complex environments for query execution.


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.