If it is I'll be jumping for joy, but as far as I know its still pretty
tied together.
Compiling the server without GWT is the easy bit, separating the existing
client from the sever code - or recreating enough to have your own client
seamlessly communicate I don't think is very easy. I don't even think
theres an up to date protocol documented anywhere.{/hopes to be wrong]~~~ Thomas & Bertines online review show: http://randomreviewshow.com/index.html Try it! You might even feel ambivalent about it :) On 2 May 2014 15:14, John Blossom <jblos...@gmail.com> wrote: > But is the app "segregated" enough now that you can still get the > functionality that one requires for concurrent edits, etc. > > All the best, > > John Blossom > > email: jblos...@gmail.com > phone: 203.293.8511 > google+: google.com/+JohnBlossom > > > On Wed, Apr 30, 2014 at 1:21 AM, Yuri Z <vega...@gmail.com> wrote: > > > Yes, you don't have to compile the GWT. > > > > > > On Wed, Apr 30, 2014 at 5:32 AM, Jim Keener <jimktra...@gmail.com> > wrote: > > > > > Is there a way to build the wave server without any of the GWT front > > > end? My end goal would be to use the Wave server over a websocket with > > > a custom (application-specific) front end. > > > > > > Jim > > > > > > > > >
