locked
AppData RemoteSettings and "HighPriority"

    Question

  • Hi,

    According to the documentation, when using the "highPriority" key to store remote settings, this should propagate the values "within one minute", but I'm finding this extremely hit and miss?

     

    Sometimes it will update as prescribed - but then when trying a second time, the settings may not be updated for perhaps 10-15 minutes (if ever getting updated at all).  When the official documents appear to recommend to using "HighPriority" to retain states such as "last page number viewed" or other such frequently changing values, how are we expected to use this in order to retain state between multiple devices and computers using the same login?

     

    Would storing such time-critical values be propagated faster if stored in the passwordVault (even if this wouldn't be recommended usage)?



    • Edited by Whinters Tuesday, September 25, 2012 4:10 PM
    Tuesday, September 25, 2012 4:09 PM

All replies

  • W,

    Make sure the case is correct.  You said "highPriority" and it should be "HighPriority".

    There is no guarantee on when the setting will be propagated but it should be given priority.  If you have true 'time-critial' information you should use another method like a webService.

    -Jeff


    Jeff Sanders (MSFT)

    Thursday, September 27, 2012 2:53 PM
    Moderator