Problem by subclassing the QIODevice

[erqsor]

If I understand how WebSockets work, they make a request over HTTP which is above the transport layer (TCP serves as the transport layer).

Yes, the client side is Google Chrome or Mozilla Firefox.
This client send the first HTTP request.
So by my side (server side), I have to get a client request (to etablish a connexion). And up to now, I used sockets to reply other requests.

You can read the ref here : http://tools.ietf.org/html/draft-iet...ketprotocol-17

Thats not "my" application. I'm making a generic API (webserver socket with Qt). So users can do simple requests or streaming, etc... (what they want...).
So for now, I give to my API users a QWsSocket with which they can communicate with different clients.

---

Added after 13 minutes:

I looked this documentation (In French, sorry) http://qt.developpez.com/doc/4.7/qnetworkaccessmanager/
And they speak about requests sended by the server to receive replies.
But here I'm doing the opposite. So if you want, I could qnetworkaccessmanager if I had to developpe a client application, but here I need to develop a server application. Thats not the server which requests the clients, but clients which requests the server.