The actual protocol implementation should be your last worry when writing a
client,
because the code required therefore is comparably small.
I just got the RPC running and it was a matter of two hours (plus one
because I was too stupid
to get varint right in the first place) If it needs to be redone ... so
what.

My client is already above 10k lines of C++ source code. The basic RPC is
less than 300.
The remaining C/S protocol code was generated by protoc for me.
The difficult part in  the client is to get the OT right and to enable a
smooth
typing experience even if two users change the same Blip.
Furthermore, I tried to implement the conversational model spec which was
much much more
work than some simple RPC.

My believe is that the entire C/S protocol thing is overrated for client
development
since it can easily be replaced later on without causing too much trouble.

Greetings
Torben


2009/10/23 Chris Casey <[email protected]>

>
> I was under the impression Google was keeping parts of the spec closed
> because it's still being created while we stress-test this alpha for
> them. They don't want people to get up a head of steam making
> something based on protocols which may well change before this hits
> beta status (or for people to create open clients relying on their
> half-baked alpha code, which could cripple the whole project going
> forward). There are *still* discussions about how exactly the client
> and server should talk to each other (XMPP vs JSON/AJAX is the most
> interesting one), so building anything other than a proof-of-concept
> client is jumping the gun a bit.
>
> >
>


-- 
---------------------------
Prof. Torben Weis
Universitaet Duisburg-Essen
[email protected]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to