Re: Re-thinking Client-Server protocol

2015-04-13 Thread Yuri Z
Well, actually I just checked and I found that Kiril already filed CCLA for Andrew. On Sun, Apr 5, 2015 at 11:02 AM Yuri Z wrote: > Sounds cool. > As already mentioned by Christian you can go ahead and add a link to > wiab.pro on demo servers page or maybe a new page for sponsors. Just make > su

Re: Re-thinking Client-Server protocol

2015-04-05 Thread Yuri Z
Sounds cool. As already mentioned by Christian you can go ahead and add a link to wiab.pro on demo servers page or maybe a new page for sponsors. Just make sure to send the ICLA for companies. On Sun, Apr 5, 2015 at 10:47 AM Andrew Kaplanov wrote: > Hi Yuri! > > I think current client-server pro

Re: Re-thinking Client-Server protocol

2015-04-05 Thread Andrew Kaplanov
Hi Yuri! I think current client-server protocol is poorly designed. - It mixes together getting of snapshots and opening of delta channels. This eliminates reconnection possibility. - All opened wavelet channels live in one protocol channel. This makes difficult separated control of channels a

Re: Re-thinking Client-Server protocol

2015-04-04 Thread Thomas Wrobel
Can you clarify #2, what connection has the GWT rich text editor have with anything else? Surely as long as the server is Java, and the client is for the web (and thus JS), you would need GWT to code share, regardless of any rich text editing or lack of :? -- One option to allow non-gwt users is to

Re-thinking Client-Server protocol

2015-04-04 Thread Yuri Z
Hi Let's us try to re-think the WIAB client-server protocol issue. >From what I remember (please correct me if I am wrong) the client interacts with server in four main ways: 1. Requests a snapshot on opening a wave 2. Sends deltas with updates 3. Receives deltas with updates. 4. Interacts directl