Skip to content

docs: plan a winter.wsgi adapter next to winter.asgi - #342

Merged
mofr merged 1 commit into
masterfrom
docs-wsgi-adapter
Oct 13, 2026
Merged

mofr merged 1 commit into
masterfrom
docs-wsgi-adapter

Conversation

@mofr

@mofr mofr commented Oct 12, 2026

Copy link
Copy Markdown
Collaborator

The architecture document planned only winter.asgi as the HTTP adapter besides Django. That bundled two separate goals: leaving Django and moving to async.

Leaving Django needs Winter's own HTTP host, and WSGI is enough for it. Winter handlers are synchronous, and winter.web.handle_request no longer depends on Django, so a WSGI adapter is small and keeps gunicorn and the current concurrency model. A WSGI host in front of Django can then take over services one URL prefix at a time.

winter.asgi stays planned for when async handlers, WebSockets or streaming are actually needed. Adapters are independent, so adding it later does not touch handlers.

Changes: winter.wsgi is added as a planned (dashed) adapter in the diagram, the layer table and the current deviations.

🤖 Generated with Claude Code

Leaving Django needs Winter's own HTTP host, and WSGI is enough for that: the handlers are
synchronous. ASGI stays planned for when async handlers, WebSockets or streaming are needed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mofr
mofr requested a review from andrey-berenda October 13, 2026 09:54
@mofr
mofr merged commit 7620a74 into master Oct 13, 2026
8 checks passed
@mofr
mofr deleted the docs-wsgi-adapter branch October 13, 2026 11:37
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.

2 participants