.NET8 Blazor new features streaming rendering
.NET8 Blazor new features streaming rendering What is SSR Streaming rendering in Blazor is combined with SSR (server-side rendering). The server assembles the HTML and returns it to the front-end, a bit like the familiar Razor Pages or MVC. Why choose Blazor to do this when you already have Razor Pages or MVC? There are several reasons for this. First of all, Razor Pages and MVC do not provide as good reusable components as Blazor. Secondly, when choosing Razor Pages or MVC, we will be locked into the SSR rendering application. If you want to add any client-side interactivity, one option is JS and another option is Blazor. So why not just use Blazor for everything? What is streaming rendering Users often encounter long and time-consuming processing, such as querying a database. The usual processing method is to wait for the long and time-consuming processing to end before responding to the browser. The user experience is relatively Difference. And streaming rendering splits the response into multiple times. The first response is quickly returned to the client, and the entire page is quickly rendered with placeholder content while performing time-consuming asynchronous operations. After the time-consuming operation is completed, the new content…
.NET8 Blazor new features streaming rendering
.NET8 Blazor new features streaming rendering What is SSR Streaming rendering in Blazor is combined with SSR (server-side rendering). The server assembles the HTML and returns it to the front-end, a bit like the familiar Razor Pages or MVC. Why choose Blazor to do this when you already have Razor Pages or MVC? There are several reasons for this. First of all, Razor Pages and MVC do not provide as good reusable components as Blazor. Secondly, when choosing Razor Pages or MVC, we will be locked into the SSR rendering application. If you want to add any client-side interactivity, one option is JS and another option is Blazor. So why not just use Blazor for everything? What is streaming rendering Users often encounter long and time-consuming processing, such as querying a database. The usual processing method is to wait for the long and time-consuming processing to end before responding to the browser. The user experience is relatively Difference. And streaming rendering splits the response into multiple times. The first response is quickly returned to the client, and the entire page is quickly rendered with placeholder content while performing time-consuming asynchronous operations. After the time-consuming operation is completed, the new content…
