Details
-
Task
-
Resolution: Done
-
P3: Somewhat important
-
None
-
None
-
None
-
8
-
Team B Foundation Sprint 57, Team B Foundation Sprint 58, Team B Foundation Sprint 59, Team B Foundation Sprint 60, Foundation Sprint 61, Foundation Sprint 62, Foundation Sprint 63, Foundation Sprint 64
Description
There should be some API review done before making qthttpserver a module. Some points:
- There are a few public final classes. Is that really needed?
- There are some APIs that accept char pointers and QByteArray's that are candidates for conversion to QByteArrayView
- int's are used as metatype ID's
- Change path formats to be compatible with std::format: https://en.cppreference.com/w/cpp/utility/format/format (Suggested by mikhailsvetkin), and add compile-time checking?
- Register custom types similar how it is done for std::format.
Attachments
Issue Links
- resulted from
-
QTBUG-95205 Assessment of what is needed to finish "Lightweight HTTP server"
- Closed
- resulted in
-
QTBUG-104538 tst_QAbstractHttpServer::websocket() memleak
- Closed
-
QTBUG-104499 Port qhttpserver away from std::bind
- Closed