GNUTLS: Basic Connection with OpenSSL

It's an interesting problem: how to make it LOOK like we're using one library, when we're actually using a completely different one? GNUTLS comes packaged with an openssl library (-l gnutls-openssl) and associated headers (gnutls/openssl.h). They do a fairly admirable job of allowing us to keep our OpenSSL code. I've noticed a couple of problems, though: BIO_set_conn_hostname()

Patterns: The Documentation Contract

When you commit to a set of documentation, you are telling all the users how your code will work and how they should use it. This has a trickle-down effect, such that any changes to the documented features can destroy entire suites of programs. Violation of the Rule Suppose you provide documentation for an early-release form