Adjust initialization lifecycle wording for stateless cases #1372
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTICE: deprioritizing this until next month. Working on two other SEPs with higher priority. Will eventually come back to this and write up a clearer example than Python's "FastMCP" for skippable init in TS or Java.
One word change:
to
...to account for SDKs skipping initialization for stateless interaction cases [ref]. In the referenced case, the Python SDK's "FastMCP" server serves requests without associating it with any session.
Motivation and Context
I imagine we all hope to see more guidance for stateless behavior going forward.
How Has This Been Tested?
generated & checked
Breaking Changes
N/A
Types of changes
Checklist
Additional context
N/A