Re: Client/server protocol and websockets

2012-01-03 Thread Davide Carnovale
Ok, then I'll check that before diving into coding, thanks! D Il giorno 03/gen/2012 21:38, "Yuri Z" ha scritto: > It seems like Walkaround has better defined and implemented c/s protocol, > so it might be a good idea to take a loot at it. > > On Tue, Jan 3, 2012 at 3:32 PM, Davide Carnovale < >

Re: Client/server protocol and websockets

2012-01-03 Thread Yuri Z
It seems like Walkaround has better defined and implemented c/s protocol, so it might be a good idea to take a loot at it. On Tue, Jan 3, 2012 at 3:32 PM, Davide Carnovale < francesco.davide.carnov...@gmail.com> wrote: > Hi Yuri, > thanks a lot for the pointer. > Before i start looking into walka

Re: Client/server protocol and websockets

2012-01-03 Thread Davide Carnovale
Hi Yuri, thanks a lot for the pointer. Before i start looking into walkaround code though i'd like to ask you something: why did you suggest this since they're using a different protocol? is there a plan to make WiaB c/s protocol adhere to walkaround one? or it was just a suggestion to where i coul

Re: Client/server protocol and websockets

2012-01-01 Thread Yuri Z
You might want also to take a look at Walkaround, as they have it has somewhat different c/s protcol implementation. On Sun, Jan 1, 2012 at 9:23 PM, Davide Carnovale < francesco.davide.carnov...@gmail.com> wrote: > Michael, > your mail is enlightening, i thou

Re: Client/server protocol and websockets

2012-01-01 Thread Davide Carnovale
Michael, your mail is enlightening, i thought websockets were "the choosen way" for wiab to talk to the world, so that's why i concentrated on that and looked for an android compatible implementation. at this point i'll reconsider using another transport, though since i already have all the pieces

Re: Client/server protocol and websockets

2012-01-01 Thread Davide Carnovale
ok, i finally had time for reading your suggestions =) repy is inline > Hi David: > > First of all, I'm not a WIAB internals expert. But as I was patching the > websocket part these months I can give you some advices: > - WIAB now uses websocket (via jetty) for clients like chrome and > socket-io

Re: Client/server protocol and websockets

2011-12-30 Thread Michael MacFadden
Davide, Again, I am not an expert on the current client server protocol, but I do have one comment to make. I think a good objective of whatever protocol we come up with is that the protocol (i.e the message syntax, message semantics, data types, etc) be separated from the transport layer. I

Re: Client/server protocol and websockets

2011-12-30 Thread Davide Carnovale
Thanks a lot for your help Vincente, I'll check everything and report back :-) D Il giorno 30/dic/2011 01:34, "Vicente J. Ruiz Jurado" ha scritto: > El 29/12/11 20:30, Davide Carnovale escribió: > > Hi all, > > I'd like to contribute to apache wave, in particular in the c/s protocol > > area, my

Re: Client/server protocol and websockets

2011-12-29 Thread Vicente J. Ruiz Jurado
El 29/12/11 20:30, Davide Carnovale escribió: > Hi all, > I'd like to contribute to apache wave, in particular in the c/s protocol > area, my ideal goal (in wave terms) is to make a working c/s protocol and > an android API that could later be used to build any kind of wave clients. > (because my g

Client/server protocol and websockets

2011-12-29 Thread Davide Carnovale
Hi all, I'd like to contribute to apache wave, in particular in the c/s protocol area, my ideal goal (in wave terms) is to make a working c/s protocol and an android API that could later be used to build any kind of wave clients. (because my general goal, outside of wave scope, is to have a special