Santiago Tortosa

From Phoenix' [handling](https://github.com/phoenixframework/phoenix/blob/master/lib/phoenix/endpoint/cowboy_websocket.ex#L69), we can observe Cowboy's semantics and how these are tackled - the `{opcode, payload}` tuple is broken down into separate arguments and applied to a handler callback....

Implementing a custom version of [this module](https://github.com/phoenixframework/phoenix/blob/master/lib/phoenix/endpoint/cowboy_websocket.ex) would be required in the case we want to be able to receive all [opcodes](https://github.com/ninenines/cowboy/blob/master/src/cowboy_websocket.erl#L45) (as Phoenix only dispatches text and binary) and...

Given that this was initially thought to act as a bridge to Cowboy and to provide all of its functionality, I have to agree that following a standardized syntax is...

I agree a better example would help a lot, this is something I will tackle as I'm done with #1. 🙂 For the record and in the meantime, I would...

@dcy [this](https://github.com/phoenixframework/phoenix/blob/7329665be6ab99a6f5d6379288fba3a6bf54b45c/lib/phoenix/endpoint/cowboy_handler.ex#L93) is what Phoenix sets as your socket path. It essentially joins the string given on the `socket` macro and the atom provided on the `transports` macro. That-is, if...

Essentially *phx_raws* serves as an utility for those who don't want to both have to add an own cowboy handler nor configure the dispatch options every time a socket is...

Adding a new branch soon. Currently trying to get round threading issues.

This rewrite is near completion - currently awaiting for access to gateway's v6 documentation so I can tweak. Issues #7 and #9 plus requests #15 and #16 are satisfied and...

Just hit you up on Discord. _litcord_ has been discontinued for quite a while now and thus is not to be used at its current state. Albeit we may go...