denoland / denoland/fastwebsockets

Pingora compatibility

Open
#104 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
1.1k
Forks
112
PR merge metrics
No merged PRs in 30d

Description

Hi,
Trying to implement websocket handling inside Pingora (instead of proxying -> some cases are better handled at the network edges without a local server that would handle the websocket part and reply to Pingora).

I understand that I can use this project src folder to parse the frame and handle the fragmentation, except handshake.rs and upgrade.rs, which are hyper/axum specific (UpgradeFut..).

I will look into it this week end but I wanted to have another opinion before I dive in.

Thanks guys

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the WebSocket frame and fragmentation code in src, then inspect handshake.rs and upgrade.rs to identify the Hyper/Axum-specific assumptions. Compare those entry points with Pingora's WebSocket handling needs. The issue does not define a concrete API, compatibility boundary, or acceptance test, so the first step is to clarify the intended scope and what compatibility would mean.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.