A Review of Multidatabase Transactions on the Web: From the ACID to the SACReD

Younas, Muhammad; Eaglestone, Barry; Holton, R.

doi:10.1007/3-540-45033-5_10

Cited by 17 publications

(20 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the performance evaluation of the classical commit protocols it is assumed that component transactions are processed in parallel [16] and hence the increase in the number of component transaction does not affect the overall processing time of a transaction. However, in context-aware transactions this assumption may not be valid due to the characteristics of M-services.…”

Section: Resultsmentioning

confidence: 99%

“…Service reservation is required in order to avoid blocking of services. As described earlier, context-aware transactions are generally of longer duration and thus it is not feasible to use the classical locking protocols such as two-phase locking [16] -where a service can be locked by a single transaction and no other transactions can access that service (e.g., a table in a restaurant) until the lock is released. In the following, we adopt the W3C Tentative Hold Protocol (THP) [7] that allows multiple transactions to tentatively reserve the same service at the same time.…”

Section: The System Architecturementioning

confidence: 99%

“…Thus, in M-services it is desirable that a transaction reacts to the contextual information and adapts its behaviour according to the changes in context. Furthermore, current approaches are generally based on the conventional ACID (Atomicity, Consistency, Isolation, Durability) criteria or ETMs (Extended Transaction Models) [16]. ACID criteria require that a transaction must not expose its intermediate results (isolation) and must be atomic (all its actions must be carried out or none is).…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A new model for context-aware transactions in mobile services

Younas

Mostéfaoui

2011

Pers Ubiquit Comput

View full text Add to dashboard Cite

With the ubiquity of handheld devices (such as smart phones and PDAs) and the availability of a wide range of mobile services (such as mobile banking, road traffic updates, and weather forecast) people can nowadays access information and conduct online transactions virtually anywhere and anytime. In such flexible, dynamic but less reliable environment, transaction management technology is believed to provide service reliability and data consistency. Indeed, in mobile and ubiquitous environments where devices as well as services can, seamlessly join and leave the ubiquitous network, transaction management can be very helpful during the recovery of services from failure. Current transaction models and commit protocols do not take into account context information. However, in mobile environments it is imperative to consider context information in the commit of a transaction -i.e., a transaction can be successfully completed if it meets the required context. In this paper we propose a new model for context-aware transactions and their performance management in mobile environments. Unlike conventional transactions, context-aware transactions adapt to the required context. By context we mean the service context as well as the user's context that includes user's needs and preferences. This paper designs and develops the proposed transaction model and evaluates its performance in terms of time and message complexities as well as transaction's throughput.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: The System Architecturementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A new model for context-aware transactions in mobile services

Younas

Mostéfaoui

2011

Pers Ubiquit Comput

View full text Add to dashboard Cite

show abstract

“…Thus, in M-services it is desirable that a transaction reacts to the contextual information and adapts its behaviour according to the changes in context. Furthermore, current approaches are generally based on the conventional ACID (Atomicity, Consistency, Isolation, Durability) criteria [16]. Such criteria require that a transaction must not expose its intermediate results (isolation) and must be atomic; all its actions must be carried out or none is.…”

Section: Introductionmentioning

confidence: 99%

“…However, we see that problematic. Accordingly, our paper proposes a relaxed set of transaction correctness criteria, called SACReD (Semantic Atomicity, Consistency, Resiliency, Durability) (previously developed in [15,16]) and a protocol for enforcing them, which it argues are more appropriate to the context-aware, more volatile, dynamic and open nature of M-services transactions. Unlike ACID criteria, SACReD do not impose isolation policy thus allowing transaction to be partially committed.…”

Section: Introductionmentioning

confidence: 99%

Context-Aware Mobile Services Transactions

Younas

Mostéfaoui

2010

2010 24th IEEE International Conference on Advanced Information Networking and Applications

View full text Add to dashboard Cite

-with the ubiquity of handheld devices people can now access information and conduct online transactions virtually anywhere and anytime. In such flexible but less reliable environment transaction management technology is believed to provide service reliability and data consistency. Existing models developed for mobile transactions mainly focus on variation of conventional commit procedures and give little or no attention to the context-awareness which has become a crucial part of modern mobile applications. Given the high availability of context-aware services, mobile transactions should not only acquire required services but should also comply with the service context. This paper exploits the service-oriented computing technology and accordingly proposes a novel approach that manages transactions using the contextual information of mobile services. The proposed approach has several advantages. It manages transactions such that they adapt to the required service context as well as user's needs. It also ensures the reliability of transactions and also increases their resilience to failures.

show abstract