Look up tables Ria Services
My application has a master database which has around 50 tables which are used as lookup tables and will provide data to fill the comboboxes and any other controls and also some application settings tables. So I was thinking of creating these master tables context and load the entities and add it to the application life time context object upon user login so that I can access them throughout the application when ever I need. However I am also thinking of a different approach where I download the dataseset of all the tables and save it to the isolated storage and read the tables from that dataset when ever I need to 开发者_运维知识库load the combobox. The dataset with all the tables loaded is around the size 1.2MB. I do not know which one should I follow and what will be the shortcomings of these approaches when compared to each other and also is there an elegant way of handling such a case. Can anyone please suggest me ?
Thanks, Ajay.
The first problem you face with any solution is synchronization when any of these 50 tables change. How would you even know if the change occurs outside the scope of both the server-side app and the Silverlight client?
I would simply opt to use output caching with RIA Services and put a reasonable cache expiration in place that ensures changes are incorporated on a somewhat reasonable interval.
http://blogs.msdn.com/b/digital_ruminations/archive/2011/01/05/ria-services-output-caching.aspx
精彩评论