Hi Keagan,
I guess we are mixing the concepts here.
You can have a "long lasting HTTP" to the server using a "keep alive" connection. This will avoid the cost of HTTP connection on each request, which is the problem since the cost of channel validation/creation will remain.
The change to specify the channel and the message on each publish will require a big change and probably it won't be compatible with the current usage, forcing a breaking change.
Currently, all the content in the body is used to compose the message, which can be a binary message (not encoded), for instance.
If you have a proposal to keep things working as they are and adding the support to specify the channel on each publish (you already can do that with the keep alive, only the WebSocket support is missing) I will be happy to review the code.
Kind regards,
Wandenberg