litespeedtech / litespeedtech/openlitespeed

enhancement ? ASGI to LSAPI ??

Open
#338 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.5k
Forks
233
Avg merge
2d 19h
Merged PRs (30d)
5

Description

Hi,

Just a suggestion.
I know there is a way to launch **WSGI** python app, but a lot of python programs will now using **ASGI**. This is the case for **_FastAPI_** for exemple. For now the only way to use it i found was with a python server like unicorne and use reverse proxy.

It will be great if we could use directly **_FastAPI_** the way is supposed to be... **_Django_**, **_Redis_**, **_Quart_** ( Flask like but async ) are now **ASGI** compatible too, and it's juste a start...

Thanks for your work and to share with us an OpenSource Version of your incredible server ;)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the existing WSGI support and its configuration path, then determine what direct ASGI support would require; done would mean ASGI applications such as FastAPI can run without a separate server and reverse proxy.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, fastapi, flask, python
Domain
api, backend
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.