cs01/gdbgui

use modern async backend

Open

#315 opened on Feb 18, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (6,592 stars) (376 forks)batch import
help wanted

Description

Is your feature request related to a problem? Please describe. Currently gdbgui's backend uses SocketIO and has a dependency on gevent, an older async implementation. Additionally, SocketIO is not needed in all websocket implementations.

Describe the solution you'd like Use a modern async backend that does not require gevent/eventlet, nor SocketIO. A good candidate is FastAPI. Another is Starlette, which FastAPI is based on.

https://fastapi.tiangolo.com/ https://www.starlette.io/

Contributor guide

Tech stack
pythonfastapi
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Python async programminggdbgui backend architectureFastAPI basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Examine the current backend implementation in gdbgui, particularly the usage of gevent and SocketIO. Research FastAPI's WebSocket support and plan a migration that removes dependencies on gevent and SocketIO. Consider using FastAPI's async capabilities and replacing SocketIO with plain WebSockets or FastAPI's built in WebSocket support.