Hi. As I've mentioned in the "Time for a Client/Server protocol" discussion ( https://groups.google.com/group/wave-protocol/browse_thread/thread/184b66dfb3b9a24d?hl=en ) a while back, I am planning to take the existing FedOne console client code, and separate its communications layer into a java library. This way people (including myself) can start making their own clients for FedOne, at least in java, and not have to wait for a complete C/S protocol to be developed (which I think is still a long way off).
I just finished setting up my development environment today, and I will be familiarizing myself with the FedOne code over the next week or two. I will post updates in this group when there is something worthy of mentioning. Anyway, I would certainly be very interested to know who else is working on which parts that are still missing from FedOne, and to coordinate my work with other contributors. There are still a lot of things missing from FedOne. We should make a detailed list on that page you've started. A client/server API (or preferably a proper C/S protocol) and persistance are the two most critical parts. ACL and client-side OT also come to mind. What else? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
