Aleksandar Fabijanic

Here's feedback: you guys have an itch. Scratch it. With all due respect to your problems, we fix things if we deem them important enough. I'm not saying we won't...

What is proposed to fix this? Sure, logging throw is not a nice experience; but, once we catch it inside, then where/how do we indicate what happened?

> My porpose is to have a transparent behavour with and without AsyncChannel. that was clear from the original post > Is it possible, to raise the exception (only) in...

All that could be carefully done. I, however, have currently no time or need for it. Unless someone else does, if you want to see it in, you'll have to...

need more information (best is code demonstrating the problem)

What's preventing you to do this: ``` ws.receiveFrame(&ws_msg[0], ws_msg.size()); ```

from what I'm reading, frames are either [read completely](https://github.com/pocoproject/poco/blob/191cbdc97e1d9de023b8a65e0dc844911c06f6a8/Net/src/WebSocketImpl.cpp#L230), or else exception is thrown; but you can express your complaint in code (fix and corresponding test) and send pull request...

I don't think we should do this - users who want non-blocking sockets can (and probably already do) make them so. Perhaps it does make sense to be non-blocking by...

We could do that, but it seems unnecessary because the end user has access to the socket and can modify its behavior any way they want in the handler. A...

I guess what @anton-barabanov is saying is that, when `readFromDevice` reads `\r\n` only, it will interpret it as the end prematurely. But I'm not sure this fix is good and...