A Reservation-Based Coordination Protocol for Web Services
ICWS '05 Proceedings of the IEEE International Conference on Web Services
Towards TransactionalWeb Services
CECW '05 Proceedings of the Seventh IEEE International Conference on E-Commerce Technology Workshops
Transactions Concurrency Control in Web Service Environment
ECOWS '06 Proceedings of the European Conference on Web Services
A tentative commit protocol for composite web services
Journal of Computer and System Sciences - Special issue: Performance modelling and evaluation of computer systems
A transaction-aware coordination protocol for web services composition
WISE'06 Proceedings of the 7th international conference on Web Information Systems
ICFEM'06 Proceedings of the 8th international conference on Formal Methods and Software Engineering
Maintaining consistency under isolation relaxation of web services transactions
WISE'05 Proceedings of the 6th international conference on Web Information Systems Engineering
Handling transactional properties in web service composition
WISE'05 Proceedings of the 6th international conference on Web Information Systems Engineering
Concurrency management in transactional web services coordination
DEXA'06 Proceedings of the 17th international conference on Database and Expert Systems Applications
The reliability of web services atomic commitment protocols
Proceedings of the 12th International Conference on Information Integration and Web-based Applications & Services
| Hi-index | 0.00 |
Executing composed Web services in a transactional way requires coordination. WS-Coordination is a specification that can be exploited in developing coordinators for various types of transactions, which are based on Web services. WS-AtomicTransaction and WS-BusinessActivity are protocols that use WS-Coordination to define coordination types for short running atomic transactions and long-duration business transactions. A drawback of these coordination protocols is that they only recover from semantic failures but not from communication and system failures. In order to avoid this disadvantage, we have exploited WS-Coordination in developing a coordinator, which also recovers from communication and system failures. This, however, requires that the coordinator as well as the participants of the protocol have to keep a log in a stable storage. In this paper, we present the protocol and illustrate its functionality by an example.