Hi Gary, Back in Jan/Feb we had OpenMAMA-2.3.2-rc1. As far as I know there was no official release of 2.3.2. Now with 2.3.3-rc1 in May, do you know if there will still be a 2.3.2 release or is 2.3.2 s

Hi Gary, Thanks for the patch. I had some minor comments which I marked inline below with [AA:] --Alireza

BTW, I noticed the following description for MAMA_MSG_TYPE_NULL in mamaMsgType. I did not see this message type having special logic associated with it in OpenMAMA MAMC/MAMACPP. From msgtype.h: /** Ke

I also think the MAMA_TRANSPORT_CONNECT_FAILED language binding is applicable and missing in C++ and it should be supported for consistency with C API. For the user not valid (not in DACS) case, the S

Update OpenMAMA site_scons logger to include stdout for build commands as well as stderr. Hence, Windows builds details of the compile/link error (if any) from MSVS CL command-line. Signed-off-by: Ali

Hi Gary, I created this Bugzilla to track this issue: http://bugs.openmama.org/show_bug.cgi?id=180 I’ll propose a patch in the next little while for the same. Regards --Alireza

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 --Alireza

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 users, I a

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 C la

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 transition to d

Hi Gary, Is the current content of ‘next’ branch what you had in mind for the 2.3.2 release? Regards, --Alireza

If subscription message is not from inbox, then there is no need to publish the initial image when processing onNewRequest or onRequest. For example, in the case of a real time market data subscriptio

For snapshot subscriptions, there is no bridge subscription callback to be called later with mamaSubscriptionImpl_onSubscriptionDestroyed. Therefore, add code to perform the additional actions for dea

Hi Gary, Thanks a lot for your response on this. Your suggestions sound good. Please see my comments to your mail inline marked with [AA:]. --Alireza

Hi Folks, I have noticed that in Mama C subscription, if a market data subscription activation callback (i.e. createAction) fails the error is not propagated in Mama subscription layer to the applicat

Either one works for me. Looking forward to the meeting. --Alireza

Great. Thanks. For this I was using primarily 64-bit Linux (Fedora 20, x86_64) and that's where I did most of the testing, including the unit testing. On Windows, I did a build for mamda with qpid for

Hi Damian, I have raised Bugzilla ticket 168 (http://bugs.openmama.org/show_bug.cgi?id=168) and provided a patch to address this for C/C++ for the first stage. Thanks. --Alireza

Signed-off-by: Alireza Assadzadeh <Alireza.Assadzadeh@...> --- mama/c_cpp/src/examples/c/mamalistencachedc.c | 26 ++++++++++++++ .../c_cpp/src/examples/cpp/mamalistencachedcpp.cpp | 40 +

Signed-off-by: Alireza Assadzadeh <Alireza.Assadzadeh@...> --- .../gunittest/c/fieldcache/fieldcachefieldtest.cpp | 60 ++++++++++++++++ .../gunittest/c/mamamsg/msgfieldvectortests.cpp |