Doug Hoyte

Good point, sorry about that. Some of the API changes are necessary. I believe removing the templated accessor methods was especially important, they frequently caused bugs. Anyway I tagged a...

I agree that these templated methods were a bad idea. I have removed them in [my lmdbxx fork](https://github.com/hoytech/lmdbxx), and documented some alternatives in the README.

In my fork of this library (https://github.com/hoytech/lmdbxx) I have made `lmdb::dbi` instances copyable. I can't think of any situation where copying the dbi would cause a bug, and in many...

You are calling `dbi.del(wtxn, ...)` *after* you are calling `wtxn.commit()`. Committing (or aborting) a transaction invalidates it. You can't then use it for subsequent operations. Either do the delete in...

My fork requires a C++17 compiler since it uses [std::string_view](https://en.cppreference.com/w/cpp/string/basic_string_view). However, C++11 code will I believe compile fine with a C++17 compiler.

Oh, and you asked about docs. You sort of have to use the LMDB C API docs: http://www.lmdb.tech/doc/ For examples of the C++ interface, you can checkout my test code,...

You are using the templated get method with std::string. Don't do that: https://github.com/drycpp/lmdbxx/issues/1 Use `lmdb::val` instead. You can then construct an `std::string` from that by copying the value from the...

You have to use it for the key too. Passing a const char* works in my fork because it implicitly creates a string_view.

seasocks is hardcoded to use epoll which, as you noticed, is linux-specific. I think you're going to have a hard-time getting it to work natively on os x. You could...

For what it's worth, I have been using seasocks behind nginx https/wss reverse proxy successfully for some time. Basically the config looks like this: http { // ... ssl_certificate directives,...