前端开发中的“乐观更新”是什么？

问题描述

我正在阅读，并且有以下段落：

我的问题是什么乐观更新在这里？

解决方案

在乐观更新中，用户界面的行为就像在从服务器收到实际确认之前成功完成更改一样 - 它乐观地认为它最终会得到确认而不是错误。这可以提供更快速的用户体验。

I'm reading the intro to redux pattern, and there is the following paragraph there:

My question is what is optimistic updates here?

解决方案

In an optimistic update the UI behaves as though a change was successfully completed before receiving confirmation from the server that it actually was - it is being optimistic that it will eventually get the confirmation rather than an error. This allows for a more responsive user experience.

这篇关于前端开发中的“乐观更新”是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！