René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Refactor handler context to be transport- and handler-type-aware","articleBody":"The current `RequestContext` / `ServerRequestContext` design has a few rough edges that warrant a dedicated refactor:\n\n1. **Request vs notification context** — Request handlers have `request_id` and `meta`, notification handlers do not. Currently `request_id` is optional (`RequestId | None`) on a single shared type, which loses type safety. Ideally these would be distinct types so request handlers get a context where `request_id` is always present, and notification handlers get one where it does not exist.\n\n2. **Transport-specific context** — The `request_context` field on `ServerMessageMetadata` is typed as `Any` because the server layer is transport-agnostic (e.g. it is a Starlette `Request` for HTTP transports, `None` for stdio). A better design would let transports provide their own typed context that handlers can access without casting.\n\nThese two concerns are related — both point toward making the context type more precise depending on how and where a handler is invoked.\n\n\u003csub\u003e[AI Disclaimer](https://gist.github.com/maxisbey/6123d132484e4c533eab519a2800693d)\u003c/sub\u003e","author":{"url":"https://github.com/maxisbey","@type":"Person","name":"maxisbey"},"datePublished":"2026-02-09T13:45:00.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/2021/python-sdk/issues/2021"}