feat: add ReadMessageAsync interface

[iluozhiqiang]

Fixes #

Summary of Changes

1. add ReadMessageAsync interface, can be used non-blocking scenarios such as epoll

PS: Make sure your PR includes/updates tests! If you need help with this part, just ask!

[ghost]

Explain in words how ReadMessageAsync is different from ReadMessage.

The only difference that I can see is that ReadMessageAsync does not panic on repeated reads on a failed connection.

[iluozhiqiang]

Thank you for your reply.
I want to use epoll events to read messages instead of blocking reading.
Maybe I need a another implement

[ghost]

I understand that you want to use epoll. Describe how this PR accomplishes that goal. What is the change in ReadMessageAsync that enables epoll? I'm not seeing it.

[iluozhiqiang]

but ReadMessage Method only read Text and Binary.
However I need ReadMessage not wait Text And Binary.
I need non-bloking read all message with the framework,
because need while read all connections

conns, err := m.poller.Wait(128)
for _, rawConn := range conns {
	conn := rawConn.(*Conn)
	//
	conn.socket.ReadMessage()
}

[ghost]

Please help us understand how this code enables non-blocking read. As far as I can tell, the code blocks on read:

• Conn.NextReaderAsync calls
  • Conn.nextReader calls
    • Conn.advanceFrame calls
      • Conn.read blocks when peeking the bufio.Reader.

Issue #481 is about enabling non-blocking read. Give a thumbs up there in support of that feature request.

[iluozhiqiang]

Sorry, my pull request was too sloppy, I'm need thinking better about it