ObjFW  History of utils/ofhttp/lang/de.json of 645ae7ac0a98dd26

The comment with the copyright already made it not pure JSON anyway. file: [d8f293a0f2] check-in: [b5d1f8fcb1] user: js, branch: trunk, size: 4929 [annotate] [blame] [check-ins using] [diff]

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: [027af9bd4c] check-in: [d30efa8bbf] user: js, branch: trunk, size: 4573 [annotate] [blame] [check-ins using] [diff]

Without this, there would be no indication of the error when using -q. file: [ed88980c09] check-in: [9c506fc995] user: js, branch: trunk, size: 4154 [annotate] [blame] [check-ins using] [diff]

This temporarily doesn't use the search domains anymore and makes CNAMEs
slightly more inefficient. The next commits will fix both. file: [9e4f95f1d1] check-in: [ee592cf603] user: js, branch: trunk, size: 4082 [annotate] [blame] [check-ins using] [diff]

This is now in alignment with the terminology of the RFC. file: [401e7794d9] check-in: [d69f7bc1ff] user: js, branch: trunk, size: 4076 [annotate] [blame] [check-ins using] [diff]