Hi all, Let me ask an question: Would anybody directly benefit from 0MQ/OpenMAMA integration? Does anybody have MAMA applications that he wants to migrate to 0MQ? Or is this just a theoretical discussion?
Martin On 11/03/2011 11:10 PM, Daniel Cegiełka wrote: > I have mixed feelings about OpenMAMA. I expressed my opinion that the > same functionality can be provided using ZeroMQ PUB/SUB +topic > filtering. I really like a clean ZeroMQ API. OpenMAMA it seems that > will have strong support, so the bridge for ZeroMQ is an opportunity, > not threat. > > MAMA was a commercial product, which belonged to the NYSE. OpenMAMA > now belongs to the Linux Foundation, so it will be developed as open > source. Cooperation with TIBCO RV or 29West, is the search for > solutions, how can you accept closed and open solutions. > > Daniel > > > 2011/11/3 Ciprian Dorin Craciun<[email protected]>: >> Before reading my comments, please take into account that I'm not >> against OpenMAMA (nor for it)... Both OpenMAMA and ZeroMQ are open >> source projects, thus if someone has "an itch" to integrate them and >> (either him or someone else) scratches it, the better for both >> communities. (Also I'm not criticizing anyone, just presenting facts >> from the available information.) >> >> But, after reading (and interpreting) the following comments, >> >> >> 2011/11/3 Daniel Cegiełka<[email protected]>: >>> In the near future will be published documentation for preparing >>> bridges for MAMA. We just have to wait. [...] >> >> (i.e. we just have to wait (as in having zero intermediary >> feedback) for a finished product (the documentation) from the >> developers...) >> >> >>> 2011/11/3 Jon Dyte<[email protected]>: >>>> [...] >>>> though I suspect >>>> many users would stick with the NYSE DataFabric , tibco rv and 29 West >>>> bridges. >>>> (Those bridges are not in the open source distro) >> >> (i.e. exactly the part of the whole thing which makes it worth is >> "closed"... but even if they were I don't think running the backends >> would be easy / cheap...) >> >> >> Contrasts (and this is an understatement) with their >> "Understanding the OpenMAMA Development Process" charta: >> ~~~~ >> OpenMAMA development is modeled extensively upon the proven Linux >> kernel development process, where developers modify project code by >> submitting patches as emails to a public mailing list. [...] >> ~~~~ >> >> (BTW there is only one patch on the `-dev` mailing list in October.) >> >> >> Also by looking at the current repository -- >> http://git.openmama.org/OpenMAMA-1.1.git -- I'm just curious to see >> how the next commit will look like... (The previous noteworthy one >> `d0c45dd6d0e7c069cd9098f81f6775596efd5cc5` is about 3MiB in size.) >> (Although this is excusable for the first code release.) >> >> >> But then again it is a young project, and maybe things are >> different than what I'm describing here. (See Jon's final remark.) >> >>>> However it does ship with a bridge to other open source middleware >>>> called Avis. >>>> http://avis.sourceforge.net/client_library.html >>>> >>>> If we could get the ZeroMQ bridge into the distribution , I don't think >>>> it could do any harm. >>>> >>>> I havent looked in detail at what is required, but as Mike replied to >>>> me, in the absence of any >>>> documentation, studying the Avis bridge is going to be the best option. >>>> >>>> Jon >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
