Does the onDestroy() guarantee that no more callbacks will be made for that subscription?
Similar to Reuters completion event.
To guarantee this it seems it must be posted as an event on the sub queue, and no more sent after that.
For destroy/create use case:
wait for onDestroy();
What issues did the sample apps have?
Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198 | M: 917.414.4613 |
Alternate Contact: CIB PIM Trading Technology Solutions NA |
openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Sam Wilson
Sent: Wednesday, February 18, 2015 3:05 PM
Subject: [Openmama-dev] Subscription onDestroy Callback
I spoke quickly with Damien about this on IRC, but I thought I should raise the question with the community at large.
What thread should the subscription's onDestroy callback be called from?
We recently switched from calling it on a thread controlled by the bridge to enqueuing it on the subscription's queue, but that seems to cause a lot of trouble for the sample applications.
Section 9 of the OpenMAMA Developer's Guide for C leaves out the onDestroy callback.
Openmama-dev mailing list