Qt Network Workshop 2016: Difference between revisions
Jump to navigation
Jump to search
(performance) |
mNo edit summary |
||
| Line 16: | Line 16: | ||
** Is there input from sales or so? | ** Is there input from sales or so? | ||
* Performance | * Performance | ||
** try to get rid of using the bearer classes (and thread) by default, they are seldomly used | ** try to get rid of using the bearer classes (and thread) by default, they are seldomly used (this would imply deprecating QNetworkAccessManager::networkAccessible()) | ||
Revision as of 13:48, 4 August 2016
Proposed Discussion Topics
- Redirection support
- Should it be on by default
- more configurable...
- The test server
- How can we get the image
- How can we add services etc.
- How can we better manage the various openssl builds?
- The variations in build options, versions etc. between the platforms and distros has got to the point of insanity
- OpenSSL 1.1 support
- What are the main use cases for QtNetwork: HTTP(S)? Are there new use cases for e.g. IoT (UDP / UPnP etc.)?
- IoT
- Identify areas of QtNetwork we should focus on (HTTP(S) / low level sockets)
- Are there areas in QtNetwork to support the IoT story?
- Is there input from sales or so?
- Performance
- try to get rid of using the bearer classes (and thread) by default, they are seldomly used (this would imply deprecating QNetworkAccessManager::networkAccessible())