This question is locked. New answers and comments are not allowed.
I don't know if this fits into this topic, but I would love to be able to do the following in my Silverlight apps:
Have a manifest of data that the app may use, and have a background thread fetch the items (via WCF asynch service calls) from the manifest one by one. It would need to synch with the UI thread so that if the UI thread needs some data that is on the manifest, it can go ahead and get it, and make sure that the background thread knows to skip this item. Also the UI thread would need to know what item the background thread is working on, in case it requires that item.
Does this make sense?
Cheers,
Helen
Have a manifest of data that the app may use, and have a background thread fetch the items (via WCF asynch service calls) from the manifest one by one. It would need to synch with the UI thread so that if the UI thread needs some data that is on the manifest, it can go ahead and get it, and make sure that the background thread knows to skip this item. Also the UI thread would need to know what item the background thread is working on, in case it requires that item.
Does this make sense?
Cheers,
Helen
1 Answer, 1 is accepted
0
Hello Helen,
Unfortunately OpenAccess does not have such functionality currently.
Also, I cannot give you a time frame for when such feature will be implemented.
However, OpenAccess has support for ADO.NET Data Services and what you could do is
expose your data through an ADO.NET Data Service which will also allow you to build this manifest that you
mention as a simple collection of URIs.
Then you can implement a simple class that reads this manifest and loads the data asynchronously.
I hope this helps.
Sincerely yours,
Jordan
the Telerik team
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Follow the status of features or bugs in PITS and vote for them to affect their priority.
Unfortunately OpenAccess does not have such functionality currently.
Also, I cannot give you a time frame for when such feature will be implemented.
However, OpenAccess has support for ADO.NET Data Services and what you could do is
expose your data through an ADO.NET Data Service which will also allow you to build this manifest that you
mention as a simple collection of URIs.
Then you can implement a simple class that reads this manifest and loads the data asynchronously.
I hope this helps.
Sincerely yours,
Jordan
the Telerik team
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Follow the status of features or bugs in PITS and vote for them to affect their priority.