mcp: improve documentation of Add*Middleware #688
+11
−5
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.
This updates the documentation comments for
AddReceivingMiddlewareandAddSendingMiddlewareto clarify how middlewares are ordered. The existing documentation is confusing and could lead one to believe middleware is applied from right to left at the time of execution (e.g. themcp-gosdk does it this way).In fact, because the wrapping is done at the time of adding and not at the time of execution, middleware is only applied in reverse order (and therefore run in order) within the set of middlewares being added together, while middleware added successively is applied on top of existing middleware and thus run in reverse order.