The funcitons for accessing shared libraries in platform.c are os dependent. This is in prepration for windows support. Signed-off-by: Mike Schonberg <mschonberg@...> ---

In preparation for windows support, machine.c contains generic code while Linux specific code is now in linux/machine.c Signed-off-by: Mike Schonberg <mschonberg@...> ---

The funcitons for manipulating environement variables are os-specific. We may want to add a generic directory for a default implemenation. This is in preparation for the windows port. Signed-off-by:

These are OS specific. wConfig remains for backwards compatibilit; however, it may be removed in the future. They all default to a no-op for Linux, but are required for different Windows builds

This is the first in a series of patches to add Windows suport. Rather than peppering the source with #ifdef osXXX blocks, os specific headers and source files go into directory with the same name as

From: Mike Schonberg <mschonberg@...> This rather large patch set introduces the changes required for Windows support. Prior to OpenMAMA, MAMA supported other operating systems (Windows and

From: Mike Schonberg <mschonberg@...> When setting up fault tolerance use "ft" as the transport name for reading properties if the call does not provide a transport. Signed-off-by: Michael

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