Hello, we would like to request an official OpenMAMA enumeration for HMS (Hardware based Messaging System) developed by BCC Group. The suggested enum values (based on the recent version 2.3.3)

The byte buffer functions in the Qpid Proton payload implementationonly recognized the handles provided by the qpid proton middlewarebridge rather than real raw byte arrays. This made the

Yeah send on the patch and we can have a look. Cheers, Glenn Glenn McClements, SVP Engineering Cell: +44 78259 58270 Adelaide Exchange, 24-26 Adelaide Street, Belfast, UK, BT2

Hi, OK if I submit the patch that for Sconscripts that allows build w/ entitlements? It can all be removed when the entitle plugin is ready. The patch adds entitle_home to the command line parms

Hi Reed, No, the open source release is not meant to be built with entitlements (though the option is there is the customer has licensed OEA). To do it properly I want to decouple OEA from from the

Hi, When building OM 2.3.3 with entitlements enabled there are some needed changes to SConscripts. I have prepared a patch (mostly adding in the oeac library), and can send that in, but wanted to

Hi Duane, OK I understand now, thanks - got confused between 'the thread on which timer events are firing' and the 'timer thread'. I have given consideration in the past to simply ripping out this

Hi Frank, The mamaTimer is only being destroyed from one thread. The problem is that thewombat timerElement is being destroyed from two threads at once, but not the mamaTimer. One of the

Hi Duane, I read this as the problem being triggered by the timer being destroyed from multiple threads is that right? If so, that is an illegal sequence of events and would constitute a bug in the

At Solace our timer implementation in our middleware bridge is very similar to that of qpid. So although my comments below are based primarily on our experience with our own middleware bridge, I

Hi Nestor, You definitely need a broker in the middle for that sort of implementation - point to point will not support that. You should be able to publish data to the same MAMA source (topic

Hi Eduardo, As discussed on IRC, this query is related to what bridge components would need wired to facilitate a traditional exchange's broadcast / refresh / gap fill requirements and there are

Hi Frank, Just to solve a similar question, is it possible to have the opposite behaviour in which multiple applications (separated instances) publish data into the same topic (or source), and only

Hi everyone, Could you help me with some questions, please? 1.- If one client or broker house made the connection when the market had been working for a short while, I mean, the client made the

No objections here, removing support for the older versions makes sense and should help reduce the overhead of supporting the middleware. I also think we should be pretty aggressive in deprecating

Hi Folks, Last call on this - if I hear no objections within a week, I'll be removing 0.5 and 0.6 support from CI and removing the backwards compatibility macros from the code. Cheers, Frank

Hi Nestor, Order book instruments are typically prefixed with a lower case ‘b’, for an example, see the bookticker example inhttp://www.openmama.org/blog/getting-started-part-2

Hello everybody, I'm trying to figure this: I want to built an OpenMAMA proxy application, similar to MamaProxy, which listen to a source for data and then publish that data in an topic again, but

There was a realloc bug in AVIS when serializing / deserializing that should be fixed with this patch. Also added a getByteBuffer implementation. Signed-off-by: Frank Quinn <fquinn.ni@...> ---

I don't think it's reasonable to expect a unit test around OpenMAMA to support this function call as the nature of transport connectivity will vary across all middlewares. In the instance of Avis, it