Smalltalk-80: the language and its implementation
Smalltalk-80: the language and its implementation
Supporting flexible and efficient tool integration
An international workshop on Advanced programming environments
Graph attribution as a specification paradigm
SDE 3 Proceedings of the third ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
Concurrency control for cooperating transactions in an object-oriented database
OOPSLA/ECOOP '88 Proceedings of the 1988 ACM SIGPLAN workshop on Object-based concurrent programming
On extending the functions of a relational database system
SIGMOD '82 Proceedings of the 1982 ACM SIGMOD international conference on Management of data
Fragtypes: A Basis for Programming Environments
IEEE Transactions on Software Engineering
A system for algorithm animation
SIGGRAPH '84 Proceedings of the 11th annual conference on Computer graphics and interactive techniques
The design of a software environment architecture based on executable process descriptions
The design of a software environment architecture based on executable process descriptions
| Hi-index | 0.00 |
Database-centered environment architectures differ significantly from file-based architectures. Consequently they require a different set of primitives for tool support. This paper describes a form of tool composition called cotools which provides many of the benefits of UNIX pipes in terms of being able to reuse existing tools in tool composites, and allowing tools to operate concurrently ad incrementally on data. However, the tool language and the composition model is tailored to provide these benefits in a database-centered environment where tools do not directly communicate with each other. The effect of communication is achieved by allowing member tools in a cotool to access common data in a coordinated manner while allowing the changes made to data by one tool immediately visible to other tools in the cotool. Since database transactions normally maintain consistency in a database by disallowing interleaved data manipulation amongst separate applications, certain modifications to the concept of transactions are required. One of goals from a systemic point of view is to allow the benefits of tool cooperation without completely violating the transactions idea, which is a very clean mechanism for maintaining data consistency in a shared data store.