On Sun, Nov 20, 2011 at 3:46 AM, Thomas Wrobel <[email protected]> wrote: > Google-gin sounds like it could simplify and separate out (at least > too some extent) the client code. > > However, is not the intended roadmap to have a standardised > client/server protocol.? A wave equivalent of pop3/imap? > If thats the case, I think thats all thats needed. Gin might be > redundant. A little "wave interface" lib could go a long way, letting > java developers make their own clients, and providing a very clear > template for porting to other platforms and code base's. > > As a GWT developer I find making front-ends relatively easy (and have > made quite a few online apps and games), yet the wave source code > keeps defeating me when I try to work with it. I feel theres a lot of > developers probably at only my skill level - very willing to help but > hitting a skill barrier and not being able to invest the time to get > past it. > > This is all assuming Gin isnt useful as a intermediate step. > [/2 cents]
Thomas, Vicente has a *need* to improve the web client. He might not have a need of a "standardised client/server protocol". He's willing to help and propose patches for that; but maybe wouldn't commit time for an improved protocol (assuming he doesn't care that much about it). That you don't have the same priorities doesn't mean his patches should be dismissed. My own priorities are much more in line with Vicente's one that with yours, so go ahead Vicente, I'd happily help reviewing those patches. -- Thomas Broyer /tɔ.ma.bʁwa.je/
