Question on publisher events and transport topic callbacks

Alpert, Reed <reed.alpert@...>



I’ve been working through the publisher events via transport topics callbacks with Solace dev.

We have a few questions and are looking for input from the dev community.


Briefly, the publisher events support 2 ways of returning events:

1.       Via callbacks passed in by the app and returning the mamaPublisher

2.       Via transport topic callbacks in cases where the mamaPublisher is not available


Bridges can use mamaTransportImpl_invokeTransportTopicCallback() to call the mama layer to make these callbacks.

However there is no queue available for these to allow the app to determine which thread the callbacks will be returned in.


I can add a new method to set the topic callbacks that includes a queue, and make the queue available to the bridges.

extern mama_status

mamaTransport_setTransportTopicCallback2 (mamaTransport transport,

                                          mamaTransportTopicCB callback,

                                          mamaQueue queue,

                                          void* closure);

extern mama_status

mamaTransport_getTransportTopicQueue (mamaTransport transport, mamaQueue* queue);


Or the queue can be added in the transport create (new create for back compat) to be available for both transport cb and topic cb and other uses.


Please let me know any preferences.






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 | reed.alpert@...

Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...



This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to for disclosures relating to European legal entities.