Mailing-List: contact openmeetings-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: openmeetings-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of solomax666@gmail.com designates
 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJmbs8gbqD_ingGcoN0Gwv-EU5hesFRXE0-4_j7fZcOBxKmP8g@mail.gmail.com>
References: 
 <CACeMiA8f5+Rz87S4rODqEF=GMRcjW+EzSzzGAHXjHoNnuaE6Hw@mail.gmail.com>
	<CAJmbs8g+FbiczthL7YNvNijay_hz=nOmfDz-2nsYHKT0Pqi1ew@mail.gmail.com>
	<CACeMiA9MkMQLD9KV8o9TuDFUJQjJziL6EseyvaX2JhCe9W4fjg@mail.gmail.com>
	<CAJmbs8i7Ud3vY9u4tsM+4dfTSSDKqot2N2xxSDeO8NXnWXEoGg@mail.gmail.com>
	<CACeMiA8GnvuC_C7k+fT7JiQNkGHZAz=BSH31FM9sZhvyZ4Bh9g@mail.gmail.com>
	<CAJmbs8gbqD_ingGcoN0Gwv-EU5hesFRXE0-4_j7fZcOBxKmP8g@mail.gmail.com>
Date: Thu, 1 Nov 2012 21:29:02 +0700
Message-ID: 
 <CAJmbs8j1F1vnePDO7kgZrksAS2xpp9AJvBMqoyq1kurAvJ9cbw@mail.gmail.com>
Subject: Re: OpenMeetings in clustering with Master/Slave - Public API Review
From: Maxim Solodovnik <solomax666@gmail.com>
To: "seba.wagner@gmail.com" <seba.wagner@gmail.com>
Cc: "openmeetings-dev@incubator.apache.org"
 <openmeetings-dev@incubator.apache.org>
Content-Type: multipart/alternative; boundary=bcaec54fbbb830e0c404cd6fd778

--bcaec54fbbb830e0c404cd6fd778
Content-Type: text/plain; charset=UTF-8

Maybe db-clustering can be used? Like MySQL supports clustering ...
On Nov 1, 2012 9:25 PM, "Maxim Solodovnik" <solomax666@gmail.com> wrote:

> Is any soap user can send such ping?
> On Nov 1, 2012 9:10 PM, "seba.wagner@gmail.com" <seba.wagner@gmail.com>
> wrote:
>
>> native Java rpc, I guess you want to serialize the objects to transfer
>> between the instances and transfer via Sockets.
>> As far as I understood we then would need to set up our own
>> SocketListener and need yet another port to communicate between the
>> instances.
>> I am rather afraid of the security flaws that we might open the door, I
>> would rather use the existing RPC Gateways that we have.
>> A simple HTTP Rest call can be quite similar in terms of runtime length.
>> After all, master and slaves do not communicate in "real time". The
>> slaves ping the master every 3 seconds and update their status. So if the
>> call takes 200 milliseconds or 400 milliseconds does not matter at this
>> point.
>>
>> Sebastian
>>
>>
>> 2012/11/1 Maxim Solodovnik <solomax666@gmail.com>
>>
>>> Ah OK. I thought of native Java rpc, but I guess you are right.
>>> Soap/rest looks so heavy :(
>>> On Nov 1, 2012 8:53 PM, "seba.wagner@gmail.com" <seba.wagner@gmail.com>
>>> wrote:
>>>
>>>> What do you mean by RPC?
>>>> REST/SOAP are actually RPC Gateways.
>>>> Also SOAP/REST is our standard RPC Gateway API.
>>>> So what additionally RPC Gateway are you refering to?
>>>>
>>>> If we "open" yet another "door" to interact with OpenMeetings we should
>>>> either make all remote calls that are available via SOAP/REST available via
>>>> that door too (or maybe I did just not understood what you mean :))
>>>>
>>>> Sebastian
>>>>
>>>>
>>>> 2012/11/1 Maxim Solodovnik <solomax666@gmail.com>
>>>>
>>>>> Maybe it make sense to use RPC instead of rest/soap? It should be
>>>>> faster. Or speed is not critical?
>>>>> On Oct 30, 2012 4:44 PM, "seba.wagner@gmail.com" <
>>>>> seba.wagner@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> we have been discussing some of the cluster approaches.
>>>>>> I have summarized some graphs and a API descriptions:
>>>>>>
>>>>>> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Cluster+Master-Slave+overview
>>>>>>
>>>>>> Sebastian
>>>>>>
>>>>>> --
>>>>>> Sebastian Wagner
>>>>>> https://twitter.com/#!/dead_lock
>>>>>> http://www.webbase-design.de
>>>>>> http://www.wagner-sebastian.com
>>>>>> seba.wagner@gmail.com
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Sebastian Wagner
>>>> https://twitter.com/#!/dead_lock
>>>> http://www.webbase-design.de
>>>> http://www.wagner-sebastian.com
>>>> seba.wagner@gmail.com
>>>>
>>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_lock
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>

--bcaec54fbbb830e0c404cd6fd778--