Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Control API #4

Open
jgraef opened this issue May 13, 2024 · 0 comments
Open

Control API #4

jgraef opened this issue May 13, 2024 · 0 comments
Labels
todo Stuff that needs to be implemented

Comments

@jgraef
Copy link
Member

jgraef commented May 13, 2024

The control API's purpose is to allow a UI to connect to skunk-cli to set filters/rules and display the inspected flows. It should also prompt the user for flows that the user wants to modify.

I'd like to use axum with websockets for the server-side. And reqwest with reqwest-websocket for the client-side.

It would be nice if we can mux that websocket into multiple channels (mpsc and oneshot). This would make it easy to e.g. send a oneshot channel to the UI for it to send back a modified request/response. remoc is a crate that provides exactly this, but they did some questionable implementation choices, and I'd like to have a minimal/light-weight implementation of this.
@jgraef jgraef mentioned this issue May 13, 2024
Open
@jgraef jgraef added the todo Stuff that needs to be implemented label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
todo Stuff that needs to be implemented
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jgraef