Hey everyone, 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

Hi Reed, Currently we have no development activity in the Java code base. Please go ahead and submit your patch(s) Thanks, Gary Gary Molloy – SR Labs Adelaide Exchange | 24-26 Adelaide

Hi, I am working with the java interface as the Metafluent vendor (market data over JMS) is adding OpenMAMA support for the Tick42/RMDS, Solace, and SRLabs bridges. I’ve prepared a patch for

Any input around this area is very welcome, especially coming from people newish to the project with a fresh pair of eyes. Questions like the below I flag for addition to the FAQ or wiki, but so if

Glenn, Thanks for your reply and confirmations. Also it sounds good about updating the wiki in this area. If you need any additional input from my side, please let me know. Regards

Hi Mathias, As Paul pointed out, what you would really want is DQPublisher for C#, but unfortunately there isn’t one at the moment. The reason for this is that that previously there hasn’t been a

Yep, the SR Labs TCP middleware does exactly as you suggest, in that there is a second disconnect call back when the reconnects have finally failed. We’ll add this note to the bridge wiki as well.

Hi, Glen and Reed, thank you for your responses. Open (2) sounds good. Given the current (2.3.x) functionality of OpenMAMA and the importance of using a consistent/safe approach for current

From what I recall there, are no .net wrappers for the DQPublisher as yet (although somewhat unfairly there are in the Java codebase!). For me as a greenfield application, it was simpler to write in

Hi, Currently, I am trying to set up a publisher for market data with OpenMAMA in C#. I wonder if there is a way to receive a notifcation every time my publisher accepts a new subscription from a

Hi, For us consistency between the bridges is the most important item. Tick42/RMDS also uses the onDisconnect/OnReconnect model (and sends STALE status for each subscription). Both Tick42

Hi Alireza, Currently for the SR Labs TCP middleware, which is the closest in behaviour to Solace we do: Option (2): (a) onDisconnect (b) onReconnect So this

Hi, From a testing perspective we’ve been building/using Next branch for some months and have no problems. Thanks, Reed. Reed Alpert |Corporate & Investment Bank | Market Data

Issues around the entitlements were brought up on the OpenMAMA Steering Committee call yesterday, so we’ll be discussing it in the next Technical Committee meeting and get a plan together. Glenn

Hi Reed, Thanks for your email, sorry for the delay in reply. I think you have touched upon 2 items here: 1. When /are there any plans for Enterprise MAMA and OpenMAMA to come into

Hi Folks, Some middleware bridges may have the capability to automatically reconnect to their messaging infrastructure after a connection failure, for example at the TCP/socket layer. In OpenMAMA

Mac OSX 10.10 introduces htonll and ntohll macros in system headers, and as such we get redefine errors when compiling. Changed port.h to only define thefunctions if below Mac OSX 10.10. Also added

Hi Gary, Have you tried looking into an alternative tool for building binary distributions? We use FPM with great success internally (humourously entitled F'ing Package Manager, no doubt because

Hi Guys, It’s looking like a fix for the RPM stuff might take a little while longer, so in the interim I’d like to get started with testing of the RC. If you’re interested and happy to get

Gary, Is it possible to include the fix for the following issues in the 2.3.2? There is a patch available for each of these. Bug 176 - MAMAC: Missing actions for snapshot subscriptions