Skip to content
New issue

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

Remove stateful prerendering #12714

Merged
merged 1 commit into from
Aug 1, 2019

Conversation

rynowak
Copy link
Member

@rynowak rynowak commented Jul 30, 2019

Fixes: #12245
Fixes: #12630

This change removes stateful pre-rendering from Server-Side Blazor. This
means that when you render a component during the initial HTTP request,
we we will no longer preserve the component instances and their
parameters. While this feature was useful, it cause serious scalability
concerns.

This means that it will now be required to register "entry-point"
components in startup similar to client-side Blazor.

@rynowak rynowak force-pushed the rynowak/remove-stateful-prerendering branch from aabe723 to a3a482b Compare July 30, 2019 00:42
@rynowak rynowak force-pushed the rynowak/remove-stateful-prerendering branch from a3a482b to 7b702df Compare July 30, 2019 02:32
@Pilchie Pilchie added the area-blazor Includes: Blazor, Razor Components label Jul 30, 2019
Copy link
Member

@dougbu dougbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues w/ the eng/ changes

@mkArtakMSFT mkArtakMSFT added tell-mode Indicates a PR which is being merged during tell-mode area-blazor Includes: Blazor, Razor Components and removed area-blazor Includes: Blazor, Razor Components tell-mode Indicates a PR which is being merged during tell-mode labels Jul 30, 2019
@rynowak rynowak force-pushed the rynowak/remove-stateful-prerendering branch 3 times, most recently from 0463028 to 41cfa1a Compare July 31, 2019 00:33
@rynowak
Copy link
Member Author

rynowak commented Jul 31, 2019

@SteveSandersonMS @javiercn - please take a look

@rynowak rynowak force-pushed the rynowak/remove-stateful-prerendering branch 2 times, most recently from 32f1338 to 5ad2679 Compare July 31, 2019 03:44
Copy link
Member

@SteveSandersonMS SteveSandersonMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving because this looks great and I don't want to holding anything up, but please check #12714 (comment). My comment there might be wrong but if it's not it's definitely worth fixing.

@rynowak rynowak force-pushed the rynowak/remove-stateful-prerendering branch 2 times, most recently from e8f5e02 to c1476cd Compare July 31, 2019 20:39
Fixes: #12245
Fixes: #12630

This change removes stateful pre-rendering from Server-Side Blazor. This
means that when you render a component during the initial HTTP request,
we we will no longer preserve the component instances and their
parameters. While this feature was useful, it cause serious scalability
concerns.

This means that it will now be required to register "entry-point"
components in startup similar to client-side Blazor.
@rynowak rynowak force-pushed the rynowak/remove-stateful-prerendering branch from c1476cd to 2c64eae Compare July 31, 2019 22:25
@rynowak rynowak merged commit 45f5090 into release/3.0 Aug 1, 2019
@ghost ghost deleted the rynowak/remove-stateful-prerendering branch August 1, 2019 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components tell-mode Indicates a PR which is being merged during tell-mode
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants