I got a few basic questions about the blip creation process. I've been working on a Android client with a group and so far we have been using a modified version of the old FedOne code (specifically we made "fedone-android-client-api-0.2.jar" by porting "fedone-client-console-0.2.jar") so I haven't had to look too much into the nitty-gritty of the communication myself. We managed to get read/write working crudely on the old server (like, 5 months old version)
Now with the changes made with WiaB, like websocket based communication, I think I need to understand the c/s protocol better in order to make our client compatible with the latest version of the server, so hence a few questions; 1. Will WiaB going forward, be focusing on just websocket communication from the client? As I understand it, the webclient at the moment uses either websockets or socket IO....is it likely that both of these will be maintained, or is Socket IO just a stop-gap till webbrowsers support websockets more universally? 2. When a client creates a new blip, how is its ID handled. Does the client create a temp ID that is then updated by the server sending back a "real" ID? Or does the server tell the client what is a new free ID in advance of blip creation? 3. Whats currently good place to start with a c/s android port? We managed to port fedone-client-console-0.2.jar before (more or less), is there a similar place we should start from thats more upto date? Or do we have to implement a protocol from scratch? We are basically interested in connection, and reading/write/edit blips - we aren't concerned with widgets or any layout related code. Thanks for any help and pointers, -Thomas Wrobel ~~~~~~ Reviews of anything, by anyone; www.rateoholic.co.uk Please try out my new site and give feedback :)
