Cheers for this Tom, looks good. Standard practice to proceed with this one - firstly can you raise a Bugzilla ticket for tracking, and secondly can you provide some tests demonstrating the use of the

Cheers for the new patch Chad, looks good. At this stage we really need two things to progress getting this into OpenMAMA - firstly, can you raise a Bugzilla ticket, just to make it a bit easier to

Cheers for these Frank, looks good. As discussed off list, we should probably stick these into a feature branch for a bit while they undergo a bit of further testing - that way we can review and make

Cheers for that Guy, this stuff looks pretty nice. We'll take a look at the changes and follow up on the Bugzilla ticket if we need any further information. Cheers, D

Cheers for that Guy, I'll take a look on the Bugzilla and get back to you there if I have any questions. Thanks, Damian

Hi, I agree, the callback to a module that can do publish checking/etc is good. I prototyped a checking module, and it works, although loading the dictionary on 1st publish has a small delay,

This patch fixes an issue where a realloc occurs for member types which the qpid bridge will typically attempt to re-use rather than create / destroy every time. This is really just MAMA Message at

This change means that the bridge is only expected to work with version 0.6 and above of proton (ideally 0.7). It also fixed several memory leaks and simplifies many areas of code which were required

We are no longer going to support proton version 0.5 which contained compiler warnings within the header (see https://issues.apache.org/jira/browse/PROTON-420) so we can re-enable -Werror in the

Broker support has now been added to the qpid proton bridge for OpenMAMA and example configuration to use it has been added to mama.properties. Note that to make use of this functionality (using qpidd

Hi Folks, As Phil reminded me today, I actually forgot to submit this, so I'll be submitting it shortly to the list for transparency, then resurrecting the feature-qpid-branch branch to contain these

Hi, My last patch had an error with strndup/strdup changes. Attached here fixed patch against 'master' branch. Guy Tick42

Hi Damian, I've prepared here a revised version of the last experimental patch to support MAMA C Unit-Tests in Visual Studio. I removed in the last version both implementation

Hi Glenn, I have applied the changes you recommended and created a new patch. Please see attached. diff --git a/mama/jni/src/c/mamapublisherjni.c b/mama/jni/src/c/mamapublisherjni.c index

Hi Glenn, I have applied the changes you recommended and created a new patch. Please see attached. diff --git a/mama/jni/src/c/mamapublisherjni.c b/mama/jni/src/c/mamapublisherjni.c index

Hello, The payload unit tests do not run on VS 2012, I have fixed this and produced a large patch with all "C" unit tests. I have prepared the patch against the 'master' (rev. 2.3.1 and

Hi Damian, I have a follow up on the bug as you asked. Regards, Guy Tick42

Hi Alpert, I like #2 more, but I still want to keep the more data model/market data/custom logic away from the core messaging part of OpenMAMA. What I’m thinking of is a hook/callback to a

Hi, Yes I agree with Ben’s comments. Here are some caveats: 1. This is a feature that is requested by our market data infrastructure team to prevent app dev teams from accidentally

Hi Frank, You right, I should specify further what we have in mind: -Of course dictionary are not mandatory, and I don't think anyone wants the "dictionary check" to be default behaviour, it has to