Supporting Cooperative Work by Conventional Database Transactions
نویسنده
چکیده
‘Computer-Supported Cooperative Work’ (CSCW) is a young, interdisciplinary research area considering applications with strong demands on multiple fields of computer technology, e.g., distributed systems and networks or multi-media systems. In this paper, we will be focusing on the information-sharing and the corresponding activity-control aspect. Here, the conventional transaction concept of database systems lacks adequate cooperation control capabilities. A database transaction is not the appropriate operational unit for the sequence of actions/operations performed by a cooperating user because the isolation property builds protective walls to concurrently active users. Given this background many new approaches to transaction modelling are making these protective walls more permeable. While most advanced transaction models continue to apply a transparent concurrency control, in groupware systems a user-centered approach to cooperation control is needed reflecting the highly dynamic work and the rich patterns of interpersonal cooperation. Therefore, we propose an explicit cooperation control. Although, database transactions do not have cooperative capabilities, we claim that they are still applicable, even in groupware applications. The work of a cooperating user contains several elementary actions. Due to preserving basic consistency, a transaction-protected execution of these elementary actions is needed. Thus, we propose to enhance the traditional transaction processing concept by an additional layer supporting explicit cooperation control. In this paper we will discuss the interplay of implicit concurrency control and explicit cooperation control using our CONCORD model (CONtrolling COopeRation in Design Environments) as a sample approach to activity modeling in groupware systems.
منابع مشابه
Emulating Cooperative Transactions upon Standard Database Systems
Complex database applications like CAD/CAM or CASE introduce the need for long duration and/or cooperative transactions. Unfortunately, commercial DBMSs generally support a flat transaction model without cooperation. While many studies have been conducted on the management of more powerful transaction models on top of existing DBMSs (e.g., workflow management), few attention has been paid on tr...
متن کاملSynchronization and Recovery in Cooperative Transactions
Traditional atomic transactions do not work well in databases used by design applications. A typical design task is divided into parallel subtasks that are interdependent. We relax the constraint of atomicity in these situations to allow cooperative transactions to work together in groups to accomplish design tasks in the database. These groups may be arbitrarily nested to form a cooperative tr...
متن کاملSemantics-Based Locking: From Isolation to Co- operation
'Advanced database applications', such as CAD/CAM, CASE, large AI applications or image and voice processing, place demands on transaction management which differ substantially from those of traditional database applications. In particular, there is a need to support 'enriched' data models (which include, for example, complex objects or version and configuration management), 'synergistic' coope...
متن کاملPerformance analysis of long-lived cooperative transactions in active DBMS
Active database management systems (ADBMS) are used in different application domains and especially for cooperative and long duration activity management. This paper deals with performance analysis of long-lived cooperative transaction processing in an ADBMS. We first briefly discuss NP-QuadLock – a concurrency control scheme for cooperative and long durational transactions in ADBMS. A restrict...
متن کاملA Transaction Mechanism for Engineering Design Databases
One primary difference between transactions in an engineering design environment and those in conventional business applications is that an engineering transaction typically lasts a much longer time. Existing proposals for supporting the long-lived engineering transactions are all based on the public/private database architecture, in which a transaction checks out design objects from the public...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 2009