Re: [xwiki-devs] Fwd: [GSoc] XDroid Platform

hi, Document API. *create()* put the page on server. If the doc includes Objects post them as well. (likely for comments tags, attatchments) * * *update(int strategy)* Update all things in Page. Throw XWikiException if page not yet created. @param : strategy values={MERGE / FORCED } OR {ALL/ OBJECTS / TAGS/...} ex: thing there are objects 0,1,2 in server page. - merge (when local doc has objects 0,1 only) - update obj 0,1 - forced (whne local doc has obj 0,1 only) - delete obj 2 in server. Update obj 0,1. usage: doc.update(MERGE || OBJECTS || TAGS) means update page, merge objects and tags. Leave the rest as it is *delete() * delete the whole document. *get()* load the doc from server *save()* save to local device *load()* load from local device Document API is not exposed directly to Client Developers. All it's methods are protected. We have a BlogDocument [extension to Document] which is exposed to the BlogClient developer. BlogDocument knows what a blog post is and it knows that it only needs to update the BlogPostClass object in the server page. It calls the super update() method with the relevant strategy. Any way the Document is not the real guy who does all these updates to server and local saves and loads. For local saves and loads it calls a DAO(data Access Object ) in our persistence lib.This DAO will call a FAO (File Access Object ) to save the documents bulk to the local file system and enter a light weight entry in the SQLite DataBase. For updating the server, Document delegate duties to ReSTfulDocumentAdapter{implements ReSTfulAdapter}.We can configure which ReST model to use in the adapter (currently only simpleXML model). Adapters convert and adapt the Document model to a rest model and call the XWikiReST API abstraction layer to update the remote server. By the way, those ReSTfulAdapter(s) do a lot of things. Convert Document to REST model.Choose an Update Strategy object for the document (passed by param in doc.update(strat)) Calls REST api abstraction inside android according to the Update strategy. They do a lot of things for an adapter.I don't know what to call it :-).An Adapter or something else ??? :-O. Also for automatic syncs with the server when the device is offline and user have made a blog post, user should be given the option to select whether to automatically do it or manually post it. For automatic sync/posting we can make android Services. Also currently the xwiki-androi-rest module does not use android native services to call server.If a user gets a phone call or something when uploading to server things might get messy.This is because android Activities are stoped and may be destroyed on these occasions.I will see if I can rectify it if I have time after the mid eval.(It may totally affect how web services are called from upper layers) Thanks Best Regards. Sasinda. On Fri, Jun 22, 2012 at 7:33 AM, sasinda rukshan <sasindarukshan(a)gmail.com>wrote;wrote: