Skip to content

Conversation

@falbrechtskirchinger
Copy link
Contributor

Add complementary stream_handler callback to response. If set, it
replaces all other content-serving mechanisms. No content-, or
range-related headers are added.

This provides a minimal interface to implement a WebSocket server.
Introduce a new request callback, stream_handler. If set, it replaces
all other content-serving mechanisms. The handler is not called in
response to HEAD or CONNECT requests, or when following a redirect.
Content-related default header fields are not added to the request.

In conjunction with a response handler, it provides a minimal interface
to implement a WebSocket client.
@falbrechtskirchinger falbrechtskirchinger marked this pull request as ready for review February 21, 2025 06:37
@falbrechtskirchinger
Copy link
Contributor Author

I fixed the test failure on Windows. It needs a rebase if/when the two stream handler PRs are merged, but otherwise, it's done.

@yhirose
Copy link
Owner

yhirose commented Jun 23, 2025

I'll close it for now. Please let me know when you work on this.

@yhirose yhirose closed this Jun 23, 2025
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