Difference between revisions of "Batch Transmission Wrapper"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 6: | Line 6: | ||
Notes: the receiver of a [[Batch Based Interaction]] shall "throw away" the batch wrapper and process the interactions contained in the batch as if these interactions were recieved sequentially as individual interactions. | Notes: the receiver of a [[Batch Based Interaction]] shall "throw away" the batch wrapper and process the interactions contained in the batch as if these interactions were recieved sequentially as individual interactions. | ||
| + | |||
| + | ==Relevant Motions== | ||
| + | (Out of Cycle, May 2006) Propose that the current Batch Transmission Wrapper be documented as a mechanism for grouping Interactions for transmission purposes only, and for the sender to determine whether or not it wishes to use a batch transmission wrapper, and allow the receiver the option of rejecting batch transmission wrappers when it chooses not to support them. (rene/Joann, 31-0-2) | ||
Latest revision as of 14:00, 5 July 2006
The Batch Transmission Wrapper is a Transmission Wrapper which is derived from the RIM class "Batch". This Wrapper is the outermost wrapper of the Composite Message Type used by Batch Based Interactions.
The batch wrapper is used for the grouping of transmissions only.
- Any interaction which uses a batch wrapper (a Batch Based Interaction) (as a whole) doesn't have Receiver Responsibilities.
- The receiver of a batch transmission may send an Accept Acknowledgement if it doesn't support batch wrappers. If a sender receives such an error message, it may want to resend the batch contents in the form of Message Based Interactions.
Notes: the receiver of a Batch Based Interaction shall "throw away" the batch wrapper and process the interactions contained in the batch as if these interactions were recieved sequentially as individual interactions.
Relevant Motions
(Out of Cycle, May 2006) Propose that the current Batch Transmission Wrapper be documented as a mechanism for grouping Interactions for transmission purposes only, and for the sender to determine whether or not it wishes to use a batch transmission wrapper, and allow the receiver the option of rejecting batch transmission wrappers when it chooses not to support them. (rene/Joann, 31-0-2)
