[Blazor server] Blazor server improvements for 6.0

[javiercn]

• More control over circuits lifetime (ability to monitor circuit activity and terminate from client/server).
• Hibernate and restore circuits.
• Better byte [] serialization.
• Render root components after circuit has started.
• Remove size limitations imposed by signalr message size.
• Specific components for dealing with large binary data (files and media).
• Specific component for dealing with large amounts of text data (InputTextArea)
• Better logging through activity tracing see
• Tooling for Blazor Server perf & load testing

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[michalczerwinski]

Are there any details on what is to be expected?

[mkArtakMSFT]

@javiercn please add more details about what to consider as part of this issue. Thanks!

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

[javiercn]

I've added some high level points, but I'll add more details if necessary.

[danroth27]

We've also heard a bunch of Blazor Server users ask for tools to help load test Blazor Server apps: #27457

[SteveSandersonMS]

I've split out each of the items that didn't already have their own issues, so this meta-issue is no longer needed.

[javiercn]

@SteveSandersonMS please keep the meta-issue around, it's what we are using to track all improvements in this area.

[javiercn]

Also @SteveSandersonMS @amarie401 is helping in this area, FYI.

[SteveSandersonMS]

please keep the meta-issue around, it's what we are using to track all improvements in this area.

Meta-issues can't really be ranked or prioritized. I'm changing it from "enhancement" to "task" at least so it doesn't show as an unranked enhancement/bug. Alternatively it could be moved to a different milestone.

Tangentially, I'm not clear on which of our planning processes make use of meta-issues.

[amarie401]

Thanks for breaking this issues out @SteveSandersonMS. I have went ahead and updated my PR to reflect the links for these newly created issues https://github.com/aspnet/specs/pull/558

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[mkArtakMSFT]

Closing as some items on this list are already done and for the rest we have existing tracking issues now.

[mrlife]

@mkArtakMSFT Hi, I was wondering if these are still something MS is considering or if they're not needed anymore or are done.

• Specific components for dealing with large binary data (files and media).
• Specific component for dealing with large amounts of text data (InputTextArea)