[Development] QtWebSockets: API advice #2

Kurt Pattyn pattyn.kurt at gmail.com
Sun Oct 27 11:16:03 CET 2013


currently the QWebSocket class (see https://qt.gitorious.org/qtplayground/websockets), emits the signals textFrameReceived() and binaryFrameReceived().
These signals are tightly connected with the way web sockets work. Too me, this feels too ‘low level’.
Wouldn’t it be better to buffer these frames, and provide a QIODevice-like streaming interface? Whenever a frame arrives, it is stored, and the signal readyRead() is emitted.

What are your thoughts?

More information about the Development mailing list