We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
刚开始开发时,注意到 Blazor Web App 即使引入了 PersistentComponentState 保持组件状态,在首次访问页面时,仍然会先触发一次服务器端渲染,然后触发一遍客户端渲染,会访问两次数据库。
PersistentComponentState
可以搜索到类似问题的反馈:dotnet/aspnetcore#59198
于是,当时采用的方案是,禁用增强导航,每次访问都从服务器端渲染,然后切换为 Web Assembly。
根据用户体验和反馈,考虑到问题的影响(首次渲染页面时,分别从服务器端和API端访问数据库两次),处在可接受的范围内,现在准备启用Blazor增强导航,以提升页面的响应速度和浏览体验(可以大幅提高切换页面时的响应速度和卡顿)。
The text was updated successfully, but these errors were encountered:
huhubun
No branches or pull requests
刚开始开发时,注意到 Blazor Web App 即使引入了
PersistentComponentState
保持组件状态,在首次访问页面时,仍然会先触发一次服务器端渲染,然后触发一遍客户端渲染,会访问两次数据库。可以搜索到类似问题的反馈:dotnet/aspnetcore#59198
于是,当时采用的方案是,禁用增强导航,每次访问都从服务器端渲染,然后切换为 Web Assembly。
根据用户体验和反馈,考虑到问题的影响(首次渲染页面时,分别从服务器端和API端访问数据库两次),处在可接受的范围内,现在准备启用Blazor增强导航,以提升页面的响应速度和浏览体验(可以大幅提高切换页面时的响应速度和卡顿)。
The text was updated successfully, but these errors were encountered: