Return-Path: X-Original-To: apmail-incubator-openmeetings-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-openmeetings-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D91DCD181 for ; Thu, 1 Nov 2012 14:41:01 +0000 (UTC) Received: (qmail 3609 invoked by uid 500); 1 Nov 2012 14:41:01 -0000 Delivered-To: apmail-incubator-openmeetings-dev-archive@incubator.apache.org Received: (qmail 3523 invoked by uid 500); 1 Nov 2012 14:41:01 -0000 Mailing-List: contact openmeetings-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: openmeetings-dev@incubator.apache.org Delivered-To: mailing list openmeetings-dev@incubator.apache.org Received: (qmail 3507 invoked by uid 99); 1 Nov 2012 14:41:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 14:41:01 +0000 X-ASF-Spam-Status: No, hits=2.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of solomax666@gmail.com designates 209.85.220.175 as permitted sender) Received: from [209.85.220.175] (HELO mail-vc0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 14:40:53 +0000 Received: by mail-vc0-f175.google.com with SMTP id p1so2791315vcq.6 for ; Thu, 01 Nov 2012 07:40:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qQ3gRmYH0/PbytRR65Xvf594NIbVeoT1onGpGfTYoT4=; b=KLOOxcQqms/hQS7ZH8kvnyfkzbRHW9UTWPEoCAzmLO1oS1yhbRbLc5fNoSIyichXDb OT0tGEdFoI7kFsQQmW6oWxZEFzyc9U9wUiYhu/ObtB66JJHWJpDKeHhmVVG9Na4vmCKK OC270XA6d858JsuG6XaMwSuOC8uXmxk+FaiZvIasWbmRTRyhCt/xnDgAgw0kW+Izx5df aUIbYMeOlOrRs++5juw8ltPpkZ9xP2oTqSeAm/cq8I1QEgTrvm/1JXByxplDCkvc7+cW bd0xsTjfAnv+piK1GXa518mgt/B0mFBsO0dr70W8R9q27/w0Z2iOd9nim5yAPtFXf6Bc VKzA== MIME-Version: 1.0 Received: by 10.220.225.138 with SMTP id is10mr22892468vcb.24.1351780832714; Thu, 01 Nov 2012 07:40:32 -0700 (PDT) Received: by 10.58.163.102 with HTTP; Thu, 1 Nov 2012 07:40:32 -0700 (PDT) Received: by 10.58.163.102 with HTTP; Thu, 1 Nov 2012 07:40:32 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 Nov 2012 21:40:32 +0700 Message-ID: Subject: Re: OpenMeetings in clustering with Master/Slave - Public API Review From: Maxim Solodovnik To: "seba.wagner@gmail.com" Cc: "openmeetings-dev@incubator.apache.org" Content-Type: multipart/alternative; boundary=14dae9ccd476591ec104cd70002f X-Virus-Checked: Checked by ClamAV on apache.org --14dae9ccd476591ec104cd70002f Content-Type: text/plain; charset=UTF-8 Sorry forgot we have only 1 db. Trying to invent simplier ways to set up cluster (without all those manual syncronisations) On Nov 1, 2012 9:31 PM, "seba.wagner@gmail.com" wrote: > Sorry I don't understand. What has db-clustering todo with the RPC Gateway > now? > > Sebastian > > > 2012/11/1 Maxim Solodovnik > >> Maybe db-clustering can be used? Like MySQL supports clustering ... >> On Nov 1, 2012 9:25 PM, "Maxim Solodovnik" wrote: >> >>> Is any soap user can send such ping? >>> On Nov 1, 2012 9:10 PM, "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 >>>> >>>>> 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" >>>>> 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 >>>>>> >>>>>>> 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 >>>> >>> > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > seba.wagner@gmail.com > --14dae9ccd476591ec104cd70002f--