As some of you know, I was planning to separate the communications layer of the FedOne console client into a separate library. As promised, I am posting this update to let you know how it's going.
Over the past week I've been going over the FedOne source code, in particular the code of the console client. I am glad to say that the client code is overall well-structured and easy to follow (I wouldn't expect any less from Google). In fact, no major changes are necessary. Mostly, the client code just needs to be cleaned up a bit and the build configuration needs to be adjusted to generate a separate library. I have divided the work into the following steps: 1. Separate the client back-end into an abstract base class and a protobuf/rpc-specific implementation. The back-end base class will be protocol-agnostic. 2. Clean up the API. 3. Create an abstract base class for the client (it's front end). Move common client logic out of the console client and into the abstract base class. 4. Clean up dependencies and adjust the build configuration to generate a separate library. I will begin working on this within the next few days. I will post further updates in this thread. -- 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.
