[Server] Simplify server extensibility with pluggable method handlers #100
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 PR makes the server extensibility model revolve around JSON-RPC method handlers instead of bespoke executor abstractions.
Motivation and Context
Changes
MethodHandlerInterfaceimplementations viaaddMethodHandler(s); they are registered ahead of built-ins so overrides win automatically.CallToolHandler,ReadResourceHandler,GetPromptHandler,CompletionCompleteHandler) were refactored to talk straight to the registry/reference infrastructure, eliminating the Tool/Resource/Prompt/Completion executor layer.JsonRpcHandlerwas simplified to operate on an injected handler list, and the builder now assembles the complete handler pipeline (including defaults) with the standard message/session factories.examples/custom-method-handlersscenario that demonstrates replacing the default list/call tool handlers end-to-end.Breaking Changes
ToolCaller*,ResourceReader*,PromptGetter*, andCompleter*classes/interfaces along withServer\Buildersetters (setToolCaller,setResourceReader,setPromptGetter).JsonRpcHandler::make()factory was deleted; construct it directly (the builder already does this).