From b3c98388a4565fd270904383368be3fb521a57da Mon Sep 17 00:00:00 2001 From: Juha Vuolle Date: Tue, 20 Feb 2024 11:07:17 +0200 Subject: [PATCH] Document QHttpHeaders::WellKnownHeaders as the recommended overloads MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ... from a performance point of view. Task-number: QTBUG-122020 Change-Id: I8a1558a46e74d740e330ad483454267f9922a5d5 Reviewed-by: Mårten Nordheim (cherry picked from commit 9e26a8c0826f0914581c3e6f8e7970aed231c8e1) Reviewed-by: Qt Cherry-pick Bot --- src/network/access/qhttpheaders.cpp | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/network/access/qhttpheaders.cpp b/src/network/access/qhttpheaders.cpp index 2f2918f8674..002ea8614cb 100644 --- a/src/network/access/qhttpheaders.cpp +++ b/src/network/access/qhttpheaders.cpp @@ -70,6 +70,13 @@ Q_LOGGING_CATEGORY(lcQHttpHeaders, "qt.network.http.headers"); \l {https://datatracker.ietf.org/doc/html/rfc9110#name-field-order} {Set-Cookie}. Due to this and the possibility of custom use cases, QHttpHeaders does not automatically combine the values. + + \section1 Performance + + Most QHttpHeaders functions provide both + \l QHttpHeaders::WellKnownHeader and \l QAnyStringView overloads. + From a memory-usage and computation point of view it is recommended + to use the \l QHttpHeaders::WellKnownHeader overloads. */ // This list is from IANA HTTP Field Name Registry