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 <[email protected]> > 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, "[email protected]" <[email protected]> > 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 <[email protected]> >> >>> 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, "[email protected]" <[email protected]> >>> 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 >>>> [email protected] >>>> >>> >> >> >> -- >> Sebastian Wagner >> https://twitter.com/#!/dead_lock >> http://www.webbase-design.de >> http://www.wagner-sebastian.com >> [email protected] >> > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
