Details
-
User Story
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
21
-
Foundation Sprint 86, Foundation Sprint 87, Foundation Sprint 88, Foundation Sprint 89, Foundation Sprint 90, Foundation Sprint 91, Foundation Sprint 92, Foundation Sprint 93, Foundations Sprint 94, Foundations Sprint 95, Foundations Sprint 96, Foundations Sprint 97, Foundations Sprint 98, Foundations Sprint 99, Foundation Sprint 100, Foundation Sprint 101, Foundations Sprint 102, Foundation Sprint 103, Foundation Sprint 104, Foundation Sprint 105, Foundation Sprint 106, Foundation Sprint 107, Foundation Sprint 108, Foundation Sprint 109
-
fef06d279 (dev), 0c17bacc5 (6.7), 18620ef85 (dev), 362d40911 (dev)
Description
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.
Attachments
Issue Links
- 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
-
- resulted in
-
QTBUG-125966 QtHttpServer: Add an additional API to add a route that will be executed asynchronously and can send data back to the client in multiple parts
-
- In Progress
-
- mentioned in
-
Page Loading...
