-----Original Message-----
From: openmama-dev-bounces@lists.openmama.org [mailto:openmama-dev-
bounces@lists.openmama.org] On Behalf Of Benjamin Taieb
Sent: Monday, January 09, 2012 8:29 AM
To: openmama-dev@lists.openmama.org
Subject: [Openmama-dev] Questions about rodmap & bridge creation

Hi,

I'm working for a hardware based MOM vendor (Solace Systems) and we are
thinking about developing a mw bridge for openMama.

I've some questions :



1)When I look at http://www.openmama.org/what-is-openmama/openmama-
roadmaps, C++ wrapper and MAMDA C++ should be released by now.

Do you have any update you can share on the roadmap ?

We are currently working on the C++ MAMA wrappers and MAMDA C++. Our intention is to have all of the components (MAMDA C++, MAMA C++, MAMA JNI, MAMDA JAVA, etc.) complete by April. MAMA C++ and MAMDA C++ will be the first to be completed. I can not commit to a specific date at this point, but I will send an update to the list when I can.

2) As previously mentioned on this list, there is no documentation at
the moment regarding building a middleware bridge. From my reading of
the avis example, below is my understanding, Mike, could you please
comment ?

I am working on the bridge documentation.

-A MW bridge implement all the stuff defined in the mamaBridgeImpl
structure, for example if the implIdentifier is sol,

This is correct. The mamaBridgeImpl structure contains all the methods required by MAMA for a fully functional bridge. Some middlewares may not support all of the functionality and return MAMA_STATUS_NOT_IMPLEMENTED. For example Avis does not implement the mama_bridgeMamaIO_create, method mentioned below because it does not have the ability to process IO events (read/write readiness on a file descriptor). In this case and some others, we may at some point add capabilities at the MAMA level for middlewares that do not support features natively.

The bridge documentation, when complete, will address which functions and capabilities are optional.

bridgeOpen of the mamaBridgeImpl struct is a pointer to solBridge_open
function...



-The signature of each function is given in bridge.h as well. For
example :

typedef mama_status (*bridgeMamaIo_create)(ioBridge* result,

void*
nativeQueueHandle,

uint32_t descriptor,

mamaIoCb action,

mamaIoType ioType,

mamaIo parent,

void* closure);



is implemented in io.c of the avis bridge :



mama_status

avisBridgeMamaIo_create(ioBridge* result,

void* nativeQueueHandle,

uint32_t descriptor,

mamaIoCb action,

mamaIoType ioType,

mamaIo parent,

void* closure)

{

*result = 0;

return MAMA_STATUS_NOT_IMPLEMENTED;

}



Thanks,



Benjamin Taieb.

Senior Systems Engineer - EMEA

9 Devonshire Square

London, EC2M 4YF

+44 203 178 5579 (w)

+44 793 995 6731 (m)

www.solacesystems.com <http://www.solacesystems.com/>

Regards,
-Mike

Please consider the environment before printing this email.

Visit our website at http://www.nyse.com

****************************************************

Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext.