Re: Windows Phone 7 Data Access Strategies: Connection detection and bandwidth

AndreaBoschin — Sat, 26 Nov 2011 22:28:55 GMT

Hi, you solution is good. Thanks for your notice. Andrea

Re: Windows Phone 7 Data Access Strategies: Connection detection and bandwidth

MisterGoodcat — Fri, 25 Nov 2011 13:30:26 GMT

Hi Andrea,

I came across a problem with this implementation: due to the caching of the network interface and state, the watchdog reports the wrong information on activation, e.g. when the app is returning from tombstoning. Scenario: the last detected connection is a wireless connection, then the application is deactivated (lock screen, for example). After returning to the app, it can take several seconds for the phone to restore a wireless connection (I observed up to 7 seconds on an Omnia 7). During that time, the watchdog still reports a working wireless connection, even though no connection is available.

I solved that by moving the code from the start/stop service events to the phone application service lifetime events, and by initializing the watchdog to a indeterminate state when the app is activated or launched, i.e. returning a network interface of Unknown and that no network is available, until the first/next reading of that data has finished and the properties can be filled with the actual values.

Hopefully this is helpful to you or other readers. Thanks for the otherwise great article!

-Peter

SilverlightShow: Windows Phone 7 Data Access Strategies: Connection detection and bandwidth Comments

Re: Windows Phone 7 Data Access Strategies: Connection detection and bandwidth

Re: Windows Phone 7 Data Access Strategies: Connection detection and bandwidth