Skip to content

Conversation

@jonathanhefner
Copy link
Member

The "Reading Resources" sections of both concepts/resources.mdx (in the User Guide) and server/resources.mdx (in the Specification) only mention reading resources via resources/read. However, the "Common URI Schemes" section of server/resources.mdx mentions that a client may fetch a resource directly from web if the resource URI has an https:// scheme. Fetching the resource directly can have performance benefits, so it's worth calling more attention to this provision.

This commit adds mention of the provision to both "Reading Resources" sections.

@jonathanhefner jonathanhefner force-pushed the mention-fetching-https-resources branch 2 times, most recently from a332958 to 1329391 Compare June 20, 2025 16:40
@dsp-ant dsp-ant requested review from a team and ihrpr September 23, 2025 21:10
@dsp-ant
Copy link
Member

dsp-ant commented Nov 24, 2025

@jonathanhefner should we still add tihs?

@domdomegg domdomegg requested review from a team as code owners November 25, 2025 19:37
dsp-ant
dsp-ant previously approved these changes Nov 25, 2025
The "Reading Resources" sections of both `concepts/resources.mdx` (in
the User Guide) and `server/resources.mdx` (in the Specification) only
mention reading resources via `resources/read`.  However, the "Common
URI Schemes" section of `server/resources.mdx` mentions that a client
may fetch a resource directly from web if the resource URI has an
`https://` scheme.  Fetching the resource directly can have performance
benefits, so it's worth calling more attention to this provision.

This commit adds mention of the provision to both "Reading Resources"
sections.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants