It would be useful to be able to use QWebSockets for implementing a WebSocket interface class that would not be events-based: specifically, what is currently missing are a getTextMessage() method and a getBinaryMessage() method to read from the reception buffer (the sendTextMessage() and sendBinaryMessage() methods are already available for sending messages). Additionally, a waitForNewConnection() method would also be nice to have (in QWebSocketServer).

I'd like to emphasize that my argument is about being able to define a procedural interface (i.e. without signals) such that an object that implements such a procedural interface is usable on systems w/o an event loop. In other words, i am only interested in being able to have a portable interface on systems both with, and without, an event loop, and i can then decide to use a QWebSockets-based implementation on systems with an event loop, and some other implementation on systems w/o an event loop (obviously, if QWebSockets does not actually require an event loop in order to implement a procedural interface, then i can use a QWebSockets-based implementation on systems both with, and without, an event loop).