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

问题描述

我正在阅读 redux 模式简介，并且那里有以下一段:

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

...考虑新需求在前端产品中变得普遍开发，例如处理乐观更新，在服务器，在执行路由转换之前获取数据，等等.

... consider the new requirements becoming common in front-end product development, such as handling optimistic updates, rendering on the server, fetching data before performing route transitions, and so on.

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

My question is what is optimistic updates here?

推荐答案

在乐观更新中，UI 表现得好像更改在收到服务器确认之前已成功完成 - 乐观的是它最终会得到确认而不是错误.这允许响应更快的用户体验.

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.

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