why wsgi?
Open
auto-migrated
Priority-Medium
Type-Defect
- Dominant language
- C
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
```
exposing the wsgi api from libevent's http seems pretty useless, because you
can't generate async responses with the wsgi api.
```
Original issue reported on code.google.com by `pet...@gmail.com` on 29 Sep 2011 at 7:26
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue concerns exposing the WSGI API from libevent's HTTP layer; start by reviewing that interface and how asynchronous responses are handled. Clarify whether the API should be removed, changed, or retained, then define the expected behavior before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100