The on interaction cache feature request mode of the ServiceFeatureTable does not cache features as expected.
最後に公開された状態: January 17, 2017ArcGIS Runtime SDK for Qt
不具合 ID 番号
BUG-000101117
送信されました
December 1, 2016
最終更新日
June 2, 2021
適用対象
ArcGIS Runtime SDK for Qt
見つかったバージョン
100.0.0
サーバー プラットフォーム
Windows
ステータス
Known Limit
開発チームによる確認後に、この問題が、Esri の管理の範囲外にあるソフトウェアの既知の制限に関するものであると判断されました。 問題の「参考情報」セクションに、さらに詳細な説明が示されていることがあります。
参考情報
The OnInteractionCache feature request mode is currently working as designed. One of the main reasons network requests continue to go out is because data could be changing on the server due to edits from other users. Limiting these requests could result in the features cached on your device to become out of date. The fact that this feature request mode contains the word "cache" may suggest that there are performance optimizations. However, while this specific mode may have some performance gains over the OnInteractionNoCache mode, which requests new features with every viewpoint change, the main benefit of using this mode is that it works well in partially connected scenarios. For example, if you lose network connection, you will still have features cached to your device, and you can continue doing your work. If you are needing to fine tune the amount of network requests that go out, you could consider the ManualCache mode, which gives you complete control over each request that is sent to the server. This mode works especially well when working in a small area, and when other users are not updating the features you are working with.
While this feature request mode is currently working as designed, we are continuing to look into ways to further optimize feature requests with the ServiceFeatureTable in an upcoming release.