ObjFW  History of src/OFHTTPClient.h of c4600793bc0eb21aa94ef95689475d844d4a85908663afb66278d243d2cd1785

The previous API could never work cleanly and would always require
hacks, as it needed intercepting all interactions of OFTCPSocket with
the raw socket and did not work at all if the OFTCPSocket had anything
in its read buffer before starting the TLS handshake. This also could
not be fixed easily, as it would have required the object to contain two
read buffers, one for the unencrypted connection and one for the
encrypted connection. There was also no clean way to perform the
handshake in a non-blocking way.

The new API is a lot cleaner and requires none of the hacks, but using
it requires slightly more work. But this is more than made up for by
making a fully asynchronous handshake possible. It uses the concept of a
stream wrapping another stream, meaning the entire connecting part is
being handled by OFTCPSocket and then the connected socket is passed off
to OFTLSStream to wrap it. This also makes for a lot cleaner separation
of concerns. file: [dfdc56fd61] check-in: [d30efa8bbf] user: js, branch: trunk, size: 7557 [annotate] [blame] [check-ins using] [diff]

Instead, add an exception to didPerformRequest, to make it more
consistent with other places. file: [428c441451] check-in: [7f102e8c95] user: js, branch: trunk, size: 7252 [annotate] [blame] [check-ins using] [diff]

It used to be a short in some places and an int in other places. file: [2c21807c55] check-in: [6e42ee482f] user: js, branch: trunk, size: 7561 [annotate] [blame] [check-ins using] [diff]

This allows ABI stability with the fragile ABI. file: [e516a827e2] check-in: [496695d778] user: js, branch: trunk, size: 7549 [annotate] [blame] [check-ins using] [diff]

It was not very useful as for any OFHTTPClient there can only be one
active request. file: [793c0b92a1] check-in: [eaf458c1e6] user: js, branch: trunk, size: 7528 [annotate] [blame] [check-ins using] [diff]

This makes it more clear that this has nothing to do with the body of
the response, as the body of the response is read from the
OFHTTPResponse itself. file: [488f1f88e1] check-in: [d375061886] user: js, branch: trunk, size: 9756 [annotate] [blame] [check-ins using] [diff]

This uses -[asyncPerformRequest:redirects:context:] under the hood and
runs a runloop until it finished. file: [baab318aa5] check-in: [f80b0d270c] user: js, branch: trunk, size: 9715 [annotate] [blame] [check-ins using] [diff]

This is in preparation for removing the body from OFHTTPRequest.
Having it as OFData that is part of the OFHTTPRequest was a bad idea, as
it does not allow streaming. file: [e93ee6e64d] check-in: [8681bba25e] user: js, branch: trunk, size: 7417 [annotate] [blame] [check-ins using] [diff]

This makes it clear that the request is handled asynchronously and makes
it possible to reintroduce a synchronous version later. file: [e0785471fb] check-in: [0319fe1eb9] user: js, branch: trunk, size: 5876 [annotate] [blame] [check-ins using] [diff]

This does not make OFHTTPClientResponse completely asynchronous yet.

Since -[initWithURL:] does not work well with an asynchronous API, it no
longer supports HTTP URLs. However, a new, asynchronous API will be
added as a replacement later on. file: [daaaeddb63] check-in: [56a18442e2] user: js, branch: trunk, size: 5874 [annotate] [blame] [check-ins using] [diff]

This is in preparation for making OFHTTPClient asynchronous. file: [b02049e5b7] check-in: [d3d4d34dad] user: js, branch: trunk, size: 5523 [annotate] [blame] [check-ins using] [diff]

Also renames +[OFHTTPCookie cookiesFromHeaders:forURL:] to
+[OFHTTPCookie cookiesWithResponseHeaderFields:forURL:] to differentiate
between request and response header fields. file: [b76c7b05e7] check-in: [8896ef883e] user: js, branch: trunk, size: 5144 [annotate] [blame] [check-ins using] [diff]

Casts are now written like types in variable declarations. file: [8fd8945807] check-in: [4af49a13c3] user: js, branch: trunk, size: 4853 [annotate] [blame] [check-ins using] [diff]

Forgot to add 2017, even though I already did quite some changes in
2017. file: [ba8c9a7683] check-in: [44f45c2e35] user: js, branch: trunk, size: 4825 [annotate] [blame] [check-ins using] [diff]

This allows ofhttp to display all headers for the redirect in verbose
mode (the change for this is included). file: [bb02a1b9bf] check-in: [a509ab7e91] user: js, branch: trunk, size: 4819 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [9fc7a1edbb] check-in: [cec0f072f8] user: js, branch: 0.8, size: 5468 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [c62fbae14a] check-in: [2a27cf3000] user: js, branch: trunk, size: 4720 [annotate] [blame] [check-ins using] [diff]

Now that we can require GCC >= 4.6, we no longer need to have a category
on OFObject that adds the optional protocol to it. file: [b45a098c16] check-in: [ba62f00fac] user: js, branch: trunk, size: 4716 [annotate] [blame] [check-ins using] [diff]

This increases the required GCC version from 4.0 to 4.6 (exception:
Apple GCC, which already supports this with >= 4.0 starting with OS X
10.5). Since even GCC 4.6 is really old by now, there is no point in
still supporting something even older and making the code ugly because
of that. While some hardware and OS support was dropped from GCC 4.6
compared to GCC 4.0, there is nothing in there that would be an
interesting target with the exception of BeOS maybe - but a port to BeOS
can also be achieved using the Haiku support. The other dropped OSes are
mostly old versions of OSes while newer ones are still being supported
(and those newer versions of those OSes still support the same
hardware). file: [ed0609a453] check-in: [48980f2297] user: js, branch: trunk, size: 4829 [annotate] [blame] [check-ins using] [diff]

This is necessary to make GCC (>= 4.6 and Apple GCC) happy as they don't
like the list of property attributes ending in a comma. file: [1d478e9a98] check-in: [80e1a9655b] user: js, branch: trunk, size: 5464 [annotate] [blame] [check-ins using] [diff]

The only places where BOOL is left are those where they are required by
the ABI. file: [157d08fbae] check-in: [c5ef582958] user: js, branch: trunk, size: 4756 [annotate] [blame] [check-ins using] [diff]

This also implements chunked transfer encoding for OFHTTPServer and adds
a property for the protocol version to OFHTTPRequest(Reply).

Additionally, this makes it possible to add an async version of
OFHTTPClient. file: [19781d2abd] check-in: [bdf9c4d96b] user: js, branch: trunk, size: 4754 [annotate] [blame] [check-ins using] [diff]

The class also has its own file now. file: [ab52e94768] check-in: [75f187cef5] user: js, branch: trunk, size: 5712 [annotate] [blame] [check-ins using] [diff]

This removes of_http_client_tls_socket_class in favor of having one
symbol for all places where TLS would be desired. file: [0ec84f966d] check-in: [1abe5a111f] user: js, branch: trunk, size: 5789 [annotate] [blame] [check-ins using] [diff]