-
User Story
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
-
21
-
Foundation PM Prioritized
The QtHttpServer by default provides event-driven response handling in a single thread.
As a developer that wants to provide a server that can handle responses concurrently, I'd like an example and documentation that shows how to implement a server that handles each request concurrently.
- depends on
-
QTBUG-105202 Route handlers returning QFuture are broken with pipelining
-
- Closed
-
- relates to
-
QTBUG-95205
Assessment of what is needed to finish "Lightweight HTTP server"
-
- Closed
-
| For Gerrit Dashboard: QTBUG-75081 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 507996,4 | QHttpServer: Document current state of asynchronous processing | dev | qt/qthttpserver | Status: MERGED | +2 | 0 |
| 525027,2 | QHttpServer: Document current state of asynchronous processing | 6.7 | qt/qthttpserver | Status: MERGED | +2 | 0 |
| 531992,17 | QHttpServer: Add tests for routes returning QFuture<QHttpServerResponse> | dev | qt/qthttpserver | Status: MERGED | +2 | +1 |
| 540518,3 | QSslServer: Add protected configureSocket function | dev | qt/qtbase | Status: ABANDONED | 0 | 0 |
| 544316,3 | QLocalServer: add protected addPendingConnection function | dev | qt/qtbase | Status: MERGED | +2 | 0 |