On 20 November 2011 10:22, Thomas Broyer <[email protected]> wrote: > 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.
Thats a bit unfair - you make it sound like I want everyone to conform to some obscure thing that's only a priority to me. My point was more: a) That Gin might will be a wasted effort if this is going to be done anyway. (as it was described to me near the start of this year as just two weeks work whenever someone will the skills commits to it). b) That the best way to improve the webclient is to separate out the wave interface so that a lot more developers can contribute too it. This is thus not about improving the c/s vs improving the webclient - its more about the best way to improve the webclient. As I have said, I want very much to leverage the skills I have to contribute in making wfp a success this would almost all be client work - I can both improve a existing webclient or work on new ones starting afresh. (something I think might need to be considered at some point) However at the moment its still monumental work to even get a simple app to login to a wave server and post a message.
