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
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-java
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 v...@ourproject.org
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
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
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
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
