移动设备上数据驱动应用程序的首选缓存策略
创建依赖于将数据移入/移出基于云的服务（因此需要连接）的移动应用程序的首选策略是什么？
当连接不稳定时，通常采用什么机制来确保同步？
所有潜在的写入操作是否都在本地排队并从终止的上传中正常恢复？
当应用程序恢复到范围内或在丢失一段时间后重新获得连接时，大多数下载/数据查询是否会重新执行？
具体指导以及培训材料/学习资源是可以接受的！
What is the preferred strategy for creating a mobile application that relies on data to be moved to/from a cloud-based service (thus requiring connectivity)?
What mechanisms are typically employed to ensure synchronization while connectivity can be less than stable?
Are all potential write operations queued locally and recover gracefully from terminated uploads?
Are most downloads/data queries just re-executed when applications are brought back in scope or regain connectivity after losing it for a while?
Specific guidance as well as training materials/study resources are acceptable!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论