On domingo, 27 de outubro de 2013 11:16:03, Kurt Pattyn wrote: > 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?
You tell us how web sockets are meant to be used. Are you supposed to read a stream off a web socket? How about multiple streams? HTTP/2.0 supports multiple streams. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
