[Development] QtWebSockets as add-on: current voting status

[Knoll Lars]

Ok, let’s keep it as an add-on for now. I’m happy with that solution as well.

When it comes to the QML API, I do agree with Simon that having compatibility with the standard JS web sockets API is important so people can re-use code. But that doesn’t have to exclude a more declarative QML API.

Cheers,
Lars


From: Kurt Pattyn <pattyn.kurt at gmail.com<mailto:pattyn.kurt at gmail.com>>
Date: Monday 20 January 2014 13:15
To: "development at qt-project.org<mailto:development at qt-project.org>" <development at qt-project.org<mailto:development at qt-project.org>>
Cc: Lars Knoll <lars.knoll at digia.com<mailto:lars.knoll at digia.com>>, Richard Moore <rich at kde.org<mailto:rich at kde.org>>, Peter Hartmann <phartmann at blackberry.com<mailto:phartmann at blackberry.com>>, Konstantin Ritt <ritt.ks at gmail.com<mailto:ritt.ks at gmail.com>>, Gladhorn Frederik <Frederik.Gladhorn at digia.com<mailto:Frederik.Gladhorn at digia.com>>, Simon Hausmann <Simon.Hausmann at digia.com<mailto:Simon.Hausmann at digia.com>>, "aalpert at blackberry.com<mailto:aalpert at blackberry.com>" <aalpert at blackberry.com<mailto:aalpert at blackberry.com>>, Kai Koehne <kai.koehne at digia.com<mailto:kai.koehne at digia.com>>
Subject: QtWebSockets as add-on: current voting status

Hi,

The majority seems to agree that this should NOT go into the QtNetwork module, but should be an add-on.
Votes so far:

Peter Hartmann: +1 - add-on
Richard Moore: +1 - add-on
Konstantin Ritt: +1 - add-on
Frederik Gladhorn: +1 - add-on
Lars Knoll: +1 - QtNetwork

Simon Hausmann has questions regarding the QML component:
"Given that there exists a web idl for Web sockets, I suggest the qml api to consist of a QML element and a Javascript constructor. The prototype and the qml element should probably have the same api, the web Standard one.
It is in our interest that third-part JS code out there using web sockets can be used seamlessly in qml.”

Maybe it is interesting to know that the API of QML module evolved from ‘function-based’ to ‘declarative-based’ after discussion with Alan Alpert. To me, the module feels fine, but there is of course much to say about the standard Web Sockets API as described in http://www.w3.org/TR/websockets/. I really don’t have an opinion here.
Of course, for a first version the QML module can be left out until the direction is clear on this.
What are your thoughts?

Cheers,

Kurt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20140120/6c0fc1b2/attachment.html>