meh.

While Erlang supports DTLS, this library doesn't at the moment. The only transport supported is TCP for now.

Unless I'm using `allow` wrong, isn't that supposed to be like "allow anything if all the checks pass"? In that case I like `allow` and `deny` the way they are...

It would make sense to just remove the websocket specific options, then pass the given options over to the underlying socket type. I'm working on this myself now because option...

@Guid75 can you try on master? Just pass the SSL/TCP options along with the other (if any) websocket options.

`key` is the only conflict, I'd rather rename it instead of having an indirection layer in the options, that's for consistence with the TCP and SSL APIs, they pass through...

Yeah, it's not wrapped yet, I have a partial implementation locally but it's not ready yet.

I thought about making `Socket.Web` active as well, but you'd end up with two processes, just to handle a connection, which might be a problem. It would also make owning...

Nah, leave it open, it's something I want to do but, as you said, is tricky to do properly. Just have to figure out the best way to go.

@yrashk I'm open to anything, but I don't see any other way than having a polling process.

What would the code look like with `gen_tcp`?