Luis Enrique Muñoz Martín

Yes, you're right. If the client specifies that it sends 4GB of the message, and it sends 3.9GB and maintains the connection open, the server must allocate that memory expecting...

IIRC, mio does not support a "multithread concept" and should be added at a higher level, creating an executor to handle the threads (as `tokio` actually does over `mio`). Instead...

Hi, I guess you're using `Tcp` or `FramedTcp` right? The way it works is how TCP works. TCP does know about reconnections. Once the channel is closed by one side...

Hi! Is this event system something `message-io` should implement in this crate as part of it, or should it be a plugin/wrapper (maybe in another project) that allows `message-io` to...

I like the idea, but I think it doesn't belong to the `message-io` project itself. It think it should be another project that wraps this and makes this join.

Hi @reison1218 , I'm glad you like it! Because we need a "common" interface for all adapters, WS works in binary mode. Nevertheless, once https://github.com/lemunozm/message-io/issues/54 was merged (thanks to @kgraefe),...

Respecting the current interface, you need to choose between one of them when creating the connection, because `send()/recv()` methods only knows about the buffer. You do not have enough information...

Given another thought on this, maybe we could have another `send_with()` and `recv_with()` that allows to pass specific transport properties, following the structure found un #54 i.e: ```rust send_with(data, TransportProp::Ws(WsMode::Text))...

There is no way to send text messages right now. I'm still open to review a PR with the required changes or discussing an idea. But I'm no longer adding...

If the server can interpret the binary message correctly, then that can be a workaround, yes