Openmama-dev@lists.openmama.org

Home Messages Hashtags Subgroups

Messages

Between

and

[PATCH] [mama] Use "ft" as default FT transport name

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

By Michael Schonberg <mschonberg@...> · #79 ·

Re: Getting a bridge build version

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

By Mark Spielman · #78 ·

Re: [Patch 1.1 1/1] OpenMAMA (C): Adding .gitignore to force git to skip known build artifacts in status summary

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

By Mark Spielman · #77 ·

Re: [Patch 1.1 1/1] OpenMAMA (C): Adding .gitignore to force git to skip known build artifacts in status summary

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 *~

By Michael Schonberg <mschonberg@...> · #76 ·

Re: Getting a bridge build version

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

By Michael Schonberg <mschonberg@...> · #75 ·

[Patch 1.1 1/1] OpenMAMA (C): Adding .gitignore to force git to skip known build artifacts in status summary

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

By Mark Spielman · #74 ·

Getting a bridge build version

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:

By Mark Spielman · #73 ·

Re: Bridge Error Code

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

By Mike Schonberg <mschonberg@...> · #72 ·

Bridge Error Code

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.

By Mark Spielman · #71 ·

[PATCH 4/4] Make sure that we load and unload bridges properly

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

By Michael Schonberg <mschonberg@...> · #70 ·

[PATCH 3/4] Added Per-bridge Reference Count

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

By Michael Schonberg <mschonberg@...> · #69 ·

[PATCH 2/4] Add mama_openWithPropertiesCount() and mama_closeCount()

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

By Michael Schonberg <mschonberg@...> · #68 ·

[PATCH 1/4] Added locking around mama_open() and mama_close()

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

By Michael Schonberg <mschonberg@...> · #67 ·

[PATCH] MAMA: Move global bridge data to struct

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

By Michael Schonberg <mschonberg@...> · #66 ·

[PATCH] Added mamaTransportImpl_setAdvisoryCauseAndPlatformInfo()

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

By Michael Schonberg <mschonberg@...> · #65 ·

[PATCH] Use Transport Properties for FT Configuration

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

By Michael Schonberg <mschonberg@...> · #64 ·

[PATCH] Initialize Callbacks structs to 0 for mamasymbolist subscriber

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@...> ---

By Michael Schonberg <mschonberg@...> · #63 ·

[PATCH] Only invoke onQuality callbck for MAMA_MSG_TYPE_MISC

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

By Michael Schonberg <mschonberg@...> · #62 ·

[PATCH] Added listenerMsgCallbackImpl_logUnknowStatus

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

By Michael Schonberg <mschonberg@...> · #61 ·

[PATCH] Renamed listenerMsgCallback_invokeErrorCallback

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

By Michael Schonberg <mschonberg@...> · #60 ·

2241 - 2260 of 2319

Home Hashtags Subgroups Terms