dhis2-devs team mailing list archive

[Araz Abishov <araz@xxxxxxxxx>]

Hi Sakchham,

Thanks for getting in touch with us!

I agree with you that ContentProvider is another way to solve this problem, but it also requires to write a lot of boilerplate code. It is up to student to decide which approach is better to follow, but then you should also justify your choice. It could be great if you could make a small research on this topic and include your ideas/conclusion in your proposal. 

If you have any other questions, do not hesitate to ask.

Best Regards,
Araz Abishov

On March 2, 2016 at 2:26:40 PM, Sakchham Sharma (sakchhams@xxxxxxxxx) wrote:

Hello,
I'm Sakchham Sharma. I intend to contribute to DHIS under GSoC '16 by implementing a unified data store for all DHIS android data capture applications. I read the summary for the above project idea and went through the github repos of the data capture applications. I quote from the summary, " “UI” or client apps which will be talking to shared database, should use android’s IPC framework called AIDL in order to query and store data."
In my opinion I feel it would be best implemented via means of a ContentProvider. I would appreciate if any developer could give his opinion on this matter.
Thank you !

_______________________________________________  
Mailing list: https://launchpad.net/~dhis2-devs  
Post to : dhis2-devs@xxxxxxxxxxxxxxxxxxx  
Unsubscribe : https://launchpad.net/~dhis2-devs  
More help : https://help.launchpad.net/ListHelp