AppData RemoteSettings和“HighPriority” [英] AppData RemoteSettings and "HighPriority"

问题描述

根据文档，当使用"highPriority"时存储远程设置的密钥，这应该"在一分钟内"传播值，但我发现这非常受欢迎？

 

有时它会按照规定更新 - 但是当第二次尝试时，设置可能不会更新大概10-15分钟（如果一直在更新） ）。  当官方文件似乎建议使用"HighPriority"时保留
状态，例如"查看的最后一页编号"或其他此类经常变化的值，我们如何使用此值来保持使用相同登录的多个设备和计算机之间的状态？

 

如果存储在passwordVault中，存储此类时间关键值会更快地传播吗？（即使这不建议使用）？

解决方案

W，

确保案例是对的。 你说"highPriority"它应该是"HighPriority"。

无法保证设置何时传播，但应优先考虑。 如果你有真正的'时间 - 批评'信息，你应该使用另一种方法，如webService。

-Jeff

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)?

解决方案

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

这篇关于AppData RemoteSettings和“HighPriority”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！