...
While the Multiple Events method continues to be supported, the Single Event method is our best practice. New functionality is being added to the Single Event method only. The following is a comparison of the two methods.
Method | Pros | Cons |
|---|
Single Event | Full range of lot selection methods available. Support for non-deliverable swap (NDS) trades. The contract and legs are always processed together (the whole trade succeeds or the whole trade fails). Batch ID can be generated by Eagle for all trade methods. All new multi-leg derivatives enhancements will utilize single event.
| Minor remapping may be required for automation. In most cases a Single Event message is a subset of a Multiple Events message, but new tags were added to support certain use cases (sending traded interest instead of allowing Eagle to calculate it, for example). Limited history of usage in production.
|
Multiple Events | | Limited lot selection methods available (FIFO, LIFO, IDLOT). Limited support for NDS trades. Can result in “broken legs” (the contract and pay leg succeed, but the receive leg fails, for example). Batch ID must be provided on the inbound message for CSV trades. New enhancements will not be added.
|
