Warn on MaximumReceiveMessageSize

[guardrex]

Fixes #27013

[guardrex]

Let's hold off on review. We're discussing this on the PU issue. We might do something different ... an INCLUDE used in the Blazor doc and the SignalR doc, for example. We might do this, but we might only do it in the SignalR doc because the Blazor doc already links to the SignalR doc for the configuration details.

[guardrex]

The PU issue was closed right in the middle of the discussion on this.

Let's go with Rick's Gambit™ ... i.e. ... Call for review! 😆

Brennan, which way would you like to go?

• Just note this on the Blazor-side, as this PR does.
• Duplicate this for the SignalR config topic. I can place it in the Description in the table at https://learn.microsoft.com/en-us/aspnet/core/signalr/configuration?view=aspnetcore-6.0&tabs=dotnet#configure-server-options. If so, I'll add it to this PR and ping u back for final review.
• Do something else.

[BrennanConroy]

• I can place it in the Description in the table at ...

Sure, similar to how ApplicationMaxBufferSize in a later table mentions memory usage can increase if the setting is changed.

[guardrex]

@BrennanConroy ... Added a remark to the table. How's it look?

[TanayParikh]

LGTM, will leave the final sign-off for @BrennanConroy

[TanayParikh]

LGTM, but I'd await @BrennanConroy's signoff.

[guardrex]

I will ... and btw ... I've talked myself out of using the explicit byte conventions for abbreviations, as you recommended, on the issue that I opened ...

#27056

I wish MS/.NET foundation would adopt the standard. What I can do is place a remark on it in the Blazor Fundamentals topic and just use "KB"/"MB"/"GB" everywhere.

I'm going to perform a universal update on that per that issue, so let's not sweat it on this PR. UPDATE: I fixed it on this PR and will address it elsewhere on another PR.

[guardrex]

@BrennanConroy ... Are you OOF? No rush ... just checking.

[guardrex]

@BrennanConroy ... Ok ... ready for another 👁️.