Open
Conversation
Uses libcurl's websocket capabilities to add support for WebSocket. Depends on lightpanda-io/zig-v8-fork#167 Issue: #1952 This is a WIP because it currently uses the same connection pool used for all HTTP requests. It would be pretty easy for a page to starve the pool and block any progress. We previously stored the *Transfer inside of the easy's private data. We now store the *Connection, and a Connection now has a `transport` field which is a union for `http: *Transfer` or `websocket: *Websocket`.
-dispatch error on abnormal close -reciprocal close message -more url validation -cleanup dead code
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Uses libcurl's websocket capabilities to add support for WebSocket.
Depends on lightpanda-io/zig-v8-fork#167 Issue: #1952
This is a WIP because it currently uses the same connection pool used for all HTTP requests. It would be pretty easy for a page to starve the pool and block any progress.
We previously stored the *Transfer inside of the easy's private data. We now store the *Connection, and a Connection now has a
transportfield which is a union forhttp: *Transferorwebsocket: *Websocket.