![]() ![]() ![]() |
![]() |
|
|
![]() ![]() ![]() ![]() ![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Return to Business and Transactions In this paper, we present a multi-version transaction model, which exploits versions to increase availability in a mobile database environment. Each transaction in our model is either in start, committed or terminated state. A transaction can start and commit at mobile host (MH) but terminates only at mobile service station (MSS). We first present a two-version model, where each data object can have two versions, one committed and the other is terminated. A read transaction is never blocked, as it is always made available either a committed or a terminated version. We have extended the model to handle multiversions. ![]() DiSC'03 © 2003 Association for Computing Machinery |