[Development] QtWebSockets: API advice #2

[Thiago Macieira]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20131027/5627d3cb/attachment.sig>