Hi, that's excellent news. As soon as something new is out I will try to adapt my client to the new protocol.
Looking forward to the patch Torben On 23 Okt., 15:38, Anthony Baxter <[email protected]> wrote: > Hi - we're all in crunch time right now for the launch of the open > federation port next week. But there's an open patch that Sam > Thorogood has in progress that refactors the current half-assed RPC > protocol into something a little less half-assed. Hopefully he will > chime in soon - we can then document it (even if it's just in a text > file in the source repository). > > > > On Fri, Oct 23, 2009 at 06:48, Torben Weis <[email protected]> wrote: > > Hi, > > > yes, I will publish the C++ code as open source. > > > In the meantime I succeeded (hopefully) in uncovering the binary format used > > in the RPC. > > Seems that every message starts with a 4 byte integer in little endian > > notation. > > It describes the size of the message. > > Then follows a varint serial number (meaning not totally clear to me > > currently) as a varint > > (see protocol buffer definition). Next is a varint which describes the > > length of the function-name. > > Next is the function-name. Next is a varint which determines the size of the > > payload. > > The payload itself is a normal protocol buffer. That's it. The next message > > follows suit. > > > However, I did not implement this, so it might still be wrong. At least the > > format > > seems to be rather straight forward. > > > Greetings > > Torben > > > 2009/10/22 Sascha <[email protected]> > > >> I am interested in this as well. With an C++ implementation, a PHP > >> implementation would become quite easy to make too. > > >> Do you plan, to publish a C++ library? > > >> On Oct 21, 5:24 pm, Torben <[email protected]> wrote: > >> > Hi, > > >> > I am working on a C++ wave client (written from scratch, no port of > >> > the java stuff). > >> > I have the GUI and basic OT stuff in place already. > >> > Now I want to connect to FedOne. I got the proto files and created the > >> > C++ code using protoc. > >> > However, Google does not ship a RPC implementation. While I can write > >> > one on my own, > >> > I need to know how the google one is encoded. > > >> > I tried to capture the TCP communication and decode it using protoc, > >> > but this seems not to > >> > work. Can anybody tell me how the RPC message is encoded? It seems to > >> > contain the name > >> > of the RPC being called, but what is the meaning of the other bytes? > > >> > Any hint is appreciated. Reverse engineering binary messages is not > >> > really fun. > > >> > Greetings > >> > Torben > > > -- > > --------------------------- > > Prof. Torben Weis > > Universitaet Duisburg-Essen > > [email protected] > > -- > Anthony Baxter, [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 -~----------~----~----~----~------~----~------~--~---
