The Web Graph Database

Changes between Version 2 and Version 3 of Transaction


Ignore:
Timestamp:
01/19/10 17:51:47 (5 years ago)
Author:
http://mylid.net/jernst
Comment:

editorial improvements

Legend:

Unmodified
Added
Removed
Modified
  • Transaction

    v2 v3  
    11= Term: Transaction = 
    22 
    3 In InfoGrid, all modifying access to [wiki:MeshObject MeshObjects] in a MeshBase must be performed within [wiki:Transaction] boundaries. Read-only access, or access for the purpose of receiving [wiki:Event Events] does not require a [wiki:Transaction]. 
     3In !InfoGrid, all modifying access to [wiki:MeshObject MeshObjects] in a MeshBase must be performed within [wiki:Transaction] boundaries. Read-only access, or access for the purpose of receiving [wiki:Event Events] does not require a [wiki:Transaction]. 
    44 
    5 Because InfoGrid "[wiki:Net]"-enabled applications can be composed of many distributed [wiki:Node Nodes] that are not necessarily even under control by the same entity, InfoGrid [wiki:Transaction Transactions] are necessarily less strict than traditional ACID transactions. They are used primary for the following reasons: 
     5Because distributed !InfoGrid applications can be composed of many distributed [wiki:Node Nodes] that are not necessarily even under control by the same entity, !InfoGrid [wiki:Transaction Transactions] are necessarily less strict than traditional ACID transactions. They are used primary for the following reasons: 
    66 * data modified during a [wiki:Transaction] only gets written to persistent storage when the [wiki:Transaction] completes. This is an efficiency measure. 
    77 * data modified during a [wiki:Transaction] only gets conveyed to another NetMeshBase via [wiki:XPRISO] once the [wiki:Transaction] completes. This simplifies processing on the receiving end, and improves efficiency.