Hi Folks, On 3rd September, we had a productive workshop session in London focused around Dynamic Bridge Loading, Entitlements Bridges and Acceptance Test Suites. We had great representation

Hi Reed, Apologies for the delay on responding. I am currently looking into the exact status of these functions and why there is a discrepancy between versions. Thanks Stuart

Hi Folks, Over the past few weeks, I have taken on a personal project to write a ZeroMQ bridge for OpenMAMA which I have just open sourced on github: https://github.com/fquinner/OpenMAMA-zmq It

Hi, OM 2.3.3 and EM 6.0.3 have the same methods for class MamaDQPublisherManager. But EM 5.0.7 has these additional methods: virtual MamaDQPublisher* getPublisher (const char *symbol);

Hi, In the OpenMAMA release file (Windows 7 x86 Binaries) the mamda include files are in subdirs, but the sample programs do not reflect this. For MamdaBookAtomicListener.cpp: #include

Classification:Public To clarify, on “For your feature are you suggesting that when you request ABC, or would send back a list of either ABC.L, ABCD or both?” Answer is that either is possible,

Hi Folks, After reviewing our current process and the number of disparate systems that we use to track and maintain OpenMAMA (Git, Bugzilla, Phabricator and Jira services), we have decided to move

Hi Folks, Please see thread below - interesting point raised about date time and theYear 2038 problem. I’ve weighed in with my thoughts, further opinions welcome… Cheers, Frank

Hi Jörg, Thanks for the patch. We'll get this into the next branch as soon as possible. Thanks, Matt Mulhern On 01/09/2015 19:39, Jörg Hansper wrote:

>I’m not really sure on the semantics of why you need different types of list requests for BOOK or GROUP symbols – is the returned data not still just a list of symbols in field

One other note related to this: While debugging, I read 4 bytes from the socket (so that the number of bytes available dropped from 423 to 419), then continued the program. This cleared the busy

I’ve been running the timer unit tests repeatedly for over a week with the patch submitted in bug 220: http://bugs.openmama.org/show_bug.cgi?id=220 MamaTimerTestCPP.ForTimer recently entered a

Classification:Public Glenn, Thanks for explaining this a bit. I’m not really sure on the semantics of why you need different types of list requests for BOOK or GROUP symbols – is the

Hi Keith, "Also, there are actually two similar subscription types that can be used: MAMA_SUBSC_TYPE_SYMBOL_LIST and MAMA_SUBSC_TYPE_SYMBOL_LIST_NORMAL The intended different use for these is not

Hi Holger The blp bridge doesn’t queue the update messages, it just sends them directly on its own thread. I’m aware that the cpp version of mamaproxy uses a detached copy of the incoming

Classification:Public With the current OpenMAMA functionality for symbol list type requests (MAMA_SUBSC_TYPE_SYMBOL_LIST), it is not possible to request a named symbol list. Any symbol name

Hi Tom, we updated our OpenMama System to 2.3.3 and tried the mamaproxycpp.cpp example with the latest tick42blp bridge version. The Program crashes calling the MamaMsg.detach() function with

This patch follows an official request for OpenMAMA enumerations for HMS (Hardware based Messaging System) developed by BCC Group. The new enum values (based on the recent version 2.3.3) are: 1.

Hey All, Hopefully you're all having a good summer, and aren't suffering too much from being back behind your desks. If you are, we have a solution for you - the OpenMAMA Steering Committee and

Hi Frank, I’d originally raised two bugs to track this issue, one against the commonTimer infrastructure to release the lock, and the other against the qpid bridge. The changes could have been