Batch Transactions
CMI Protocol interprets a transaction request to be of the type batch if a property batchID
is defined in AESchema. All requests with the same batchID
is executed one by one, according to the sequence in which they have been received. Batch transactions adhere to the following rules:
• | Explicit sessions are not allowed: all batch requests use only implicit sessions. |
• | Currently, batch transactions are allowed to write data, but not to read. |
• | Allowed actions for batch transactions are EXECUTE and CANCEL (used to execute or cancel a batch execution). |
• | Stored batch requests never time out or get deleted, unless an explicit request is received. Such request can be either a private message, or it can be triggered from the GUI. |
• | Upon receiving a batched data access request, CMI Protocol executes validation tasks involved with parsing payload: validating the private message header, user logins and passwords; validating the payload against the XML schema; and so on. These basic validation tasks won’t be repeated at execution time. |
For more details, see Private Messages in Batch Transactions.