Mike, I believe it makes most sense for me to use the mama/version.h as it seems to be the correct place to get version information. One follow on question. Why even in the tar package I downloaded

Hi Mike, I appreciate the feedback. Below is an updated patch. Let me know if there are any other suggested edits. Cheers, Mark --------- This patch introduces a .gitignore file to force git to

This is very useful. I would remove mama/c_cpp/config.h.in~ and add *~ and *.swp for temporary files generated by vi. -Mike # Temporary Files ################# *.swp *~

It is largely up to the bridge implementor; however, it makes sense to identify both the version of the bridge code and the underlying middleware if it is available. Avis does not provide version

This patch introduces a .gitignore file to force git to skip known build artifacts when displaying status information. Signed-off-by: Mark Spielman <mark.spielman@...> --- diff --git

I’m interested in any best practices for getting a build version to report as part of the bridgeImpl->bridgeGetVersion() method. I’ve found what looks to be a reasonable version in the file:

Mark, MAMA_STATUS_PLATFORM is used forgeneric bridge errors. It might be useful to add some more specific error codesas well. Regards, -Mike

I am in the process of implementing a bridge support for a new middleware component in openMAMA. During implementation I have a need to return a sensible mama_status code for a generic bridge error.

From: Mike Schonberg <mschonberg@...> These changes ensure that we hold the lock while opening and closing payload and messaging brdiges. Additionally, we store the shared library handles so we

From: Mike Schonberg <mschonberg@...> Added a reference count to mamaBridgeImpl struct. mama_start() and mama_stop() increment and decrement this reference count to determine when initialization

From: Mike Schonberg <mschonberg@...> These methods take an additonal unsigned int* parameter that upon return contains the the reference count for mama_openXXX() and mama_closeXXX(). This allows

From: Mike Schonberg <mschonberg@...> Improved the reference counting logic and added locking around mama_open() and mama_close(). The change ensures that all initialization (one-time) and

From: Mike Schonberg <mschonberg@...> This is in preparation for adding improved reference counting and locking around mama_open(), and mama_close() to enable them to be called safely

From: Mike Schonberg <mschonberg@...> This method allows bridges to pass middleware specific details regarding errors and events. Signed-off-by: John Gray <jgray@...> ---

From: Mike Schonberg <mschonberg@...> Currently, the FT setup code uses the hard-coded transport name, "ft", to read properties from mama.properties despite the fact that the caller supplies

From: Mike Schonberg <mschonberg@...> This avoids a potentional sgmentation fault in the event that an uninitialized callback gets invoked. Signed-off-by: John Gray <jgray@...> ---

From: Mike Schonberg <mschonberg@...> When amessage arrives with a status of POSSIBLY_STALE, verify that the message type is MAMA_MSG_TYPE_MISC. This behavior is consistent with OpenMAMA

From: Mike Schonberg <mschonberg@...> This method refactors repeated logging statements and make the source easier to follow. Signed-off-by: Micheal Schonberg <mschonberg@...> ---

From: Mike Schonberg <mschonberg@...> Renamed listenerMsgCallbackImpl_invokeErrorCallback to listenerMsgCallbackImpl_invokeErrorCallback because it is an internal method. The method is also

From: Mike Schonberg <mschonberg@...> Middleware bridges pass this status to the mamaSubscription onError callback when the middleware detects a gap: