Is there an implementable design anywhere for how a client/server split would work?
It continually comes up as a blocking point preventing people from working on Wave, though I'm not familiar with plans for fixing it that maintain all required constraints. e.g. sharing business logic between client/server (and also any java client, like Android) was a large reason to use GWT originally. I don't believe there's a good way to drop that without introducing lots of incompatability issues - so the choices would be to switch to some other code-sharing system (e.g. nodeJS serverside like sharejs, although this doesn't feel much better), or stick with GWT client-side but provide a wrapper of the OT code that presents a cleaner JS API that people can write on top of. I'd recommend the latter, but for that to happen would require a chunk of work, and a good API design that actually addresses the desires of the people wanting to write client-side code against it. On 25 March 2015 at 21:29, Vicente J. Ruiz Jurado <v...@ourproject.org> wrote: > El 25/03/15 a las 21:03, Andrew Kaplanov escribió: > >> I patched this review before > > I don't see your comments in the https://reviews.apache.org/r/22776/. > > The review was closed. I patched here: > https://reviews.apache.org/r/28724/ > > > Could you create Jira issue about the problem with shortcuts? > > Done. > > PS: Andrew, if you have some spare time, please comment my last > reviews/patchs (also related with this thread): > https://reviews.apache.org/r/31900/ > https://reviews.apache.org/r/31837/ > and: > > http://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201412.mbox/%3c5483011f.1030...@ourproject.org%3E > >
