qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Etienne Antoniutti Di Muro <etienne.antoniu...@adaptivebytes.com>
Subject Re: Implementing clustering support for Qpid Java broker
Date Mon, 20 Sep 2010 15:25:07 GMT
So maybe we ca do the reverse, i.e. build a single replication
middleware serving both the C++ and Java
brokers.

Such middleware can be built on top of a specific communication
service layer, i.e. spread.


Regards
Etienne



On Mon, Sep 20, 2010 at 5:05 PM, Kerry Bonin <kerrybonin@gmail.com> wrote:
> On the C++ Broker, just remember that the technology choice made for
> clustering (OpenAIS/Corosync) is a Linux only solution, and that
> codebase (~100k SLOC) was not written for portability.
>
> Our project needs a Windows option, and this is already hurting us.  I
> (and my team) would be willing to spend some cycles supporting any
> reasonable effort to address this, even if its not C++...
>
>
> On Sun, Sep 19, 2010 at 4:18 AM, Lahiru Gunathilake <glahiru@gmail.com> wrote:
>> On Sun, Sep 19, 2010 at 11:37 AM, Etienne Antoniutti Di Muro <
>> etienne.antoniutti@adaptivebytes.com> wrote:
>>
>>> Andrew,
>>>
>>> I'll have a look at services provided by Terracotta,
>>> however at a first glance, I hit the search button on their site, with
>>> 'virtual synchrony' - no result!
>>> While if you google 'spread.org: virtual synchrony' -it's there.
>>>
>>> I'll take some time to investigate deeper into Terracotta services.
>>>
>>> However it all depends on what clustering is intended for.
>>>
>>> Moreover, in order to keep the project compact, does it make sense
>>> building a java API
>>> for the C++ broker clustering solution ?
>>>
>> I think there's C++ broker clustering already done ! I would like to use
>> another Apache project like Tribes.
>>
>>
>> Lahiru
>>
>> Lahiru
>>
>>>
>>> Regards
>>> Etienne
>>>
>>>
>>> On Thu, Sep 16, 2010 at 8:57 AM, Andrew Kennedy
>>> <andrewinternational@gmail.com> wrote:
>>> > On 15 Sep 2010, at 22:56, Etienne Antoniutti Di Muro wrote:
>>> >>
>>> >> However I do have some proposals, you can have a look here
>>> >> http://portal.acm.org/citation.cfm?id=1101143
>>> >>
>>> >> As a starter, I'd need someone to help me understand Qpid architecture,
>>> at
>>> >> least an overview.
>>> >
>>> >
>>> > For those of us that aren't paying for an ACM subscription, Etienne's
>>> thesis
>>> > is also available here:
>>> >
>>> >
>>> >
>>> http://middleware05.objectweb.org/WSProceedings/DoctoralSymposium05/a3-diMuro.pdf
>>> >
>>> > I think that functional homogeneity could probably be provided by
>>> Terracotta
>>> > or similar, but I am unsure of the licensing restrictions.
>>> >
>>> > Andrew.
>>> > --
>>> > -- andrew d kennedy ? do not fold, bend, spindle, or mutilate ;
>>> >
>>> > ---------------------------------------------------------------------
>>> > Apache Qpid - AMQP Messaging Implementation
>>> > Project:      http://qpid.apache.org
>>> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> Apache Qpid - AMQP Messaging Implementation
>>> Project:      http://qpid.apache.org
>>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message