In my AP, we serialize the data locally for offline use. To ensure that the app is always up to date, I close an update on the launch.
To do this, I have a set of WCF services that will get a delta for the requested data. Instead of keeping things confused, one service to update events, one service to update the steps, a service etc. to update the tasks is used. This means that daisies bring these calls in the callback so that they can run one after the other.
The problem with this is that they can take some time to update and it seems that they have to do this in such a way.
What do I need here to get the updates / favorites to multiple updates?
Cheers
w: //
Crackletics ( ) And as well as I have worked on some other enterprise apps, I run two service calls at the same time instead of the second one at the same time.
I have spent a lot of time making calls once-in-a-time versus two-one-time versus three-one-one-time, and once the best results got under 2G Running 2 threads in 3G On wireless, I can start together like a 8-10 thread and they will actually run fast.
In addition to those two calls, Crackets also downloaded some of Google's charts as those 2 calls at the same time, but I did not see any effect on it.
For implementation, I have a main square that controls all the webservices class and when they should be started and should be completed
similarly, though It is to know that when the web service call should be canceled, though; For example, if you are downloading data for a table, but users visit any other screen, you should immediately cancel the call, so it does not affect the download of data on the next screen.
Hope this helps.
Comments
Post a Comment