Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.

Qt Network Workshop 2016: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
Line 1: Line 1:
== Proposed Discussion Topics ==
== Proposed Discussion Topics ==


* Redirection support
# Redirection support
** Should it be on by default
#* Should it be on by default
** more configurable...
#* more configurable...
* The test server
# The test server
** How can we get the image - should we replace / update it? The Vagrant solution?
#* How can we get the image - should we replace / update it? The Vagrant solution?
** How can we add services etc.
#* How can we add services etc.
* How can we better manage the various openssl builds?
# 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
#* The variations in build options, versions etc. between the platforms and distros has got to the point of insanity
* OpenSSL 1.1 support
# 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.)?
# What are the main use cases for QtNetwork: HTTP(S)? Are there new use cases for e.g. IoT (UDP / UPnP etc.)?
* IoT
# IoT
** Identify areas of QtNetwork we should focus on (HTTP(S) / low level sockets)
#* Identify areas of QtNetwork we should focus on (HTTP(S) / low level sockets)
** Are there areas in QtNetwork to support the IoT story?
#* Are there areas in QtNetwork to support the IoT story?
** 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 (this would imply deprecating QNetworkAccessManager::networkAccessible())
#* try to get rid of using the bearer classes (and thread) by default, they are seldomly used (this would imply deprecating QNetworkAccessManager::networkAccessible())
* New in 5.8
# New in 5.8
** HTTP/2
#* HTTP/2
** OAuth 1+2
#* OAuth 1+2
* Providing widgets for QtNetwork
# Providing widgets for QtNetwork
** What to do about dependencies?
#* What to do about dependencies?
** What should we include?
#* What should we include?
** URLBar widget (danimo)
#* URLBar widget (danimo)
** SSL configuration widget (rich)
#* SSL configuration widget (rich)
** What about a certificate dialog?
#* What about a certificate dialog?

Revision as of 11:22, 17 August 2016

Proposed Discussion Topics

  1. Redirection support
    • Should it be on by default
    • more configurable...
  2. The test server
    • How can we get the image - should we replace / update it? The Vagrant solution?
    • How can we add services etc.
  3. 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
  4. OpenSSL 1.1 support
  5. What are the main use cases for QtNetwork: HTTP(S)? Are there new use cases for e.g. IoT (UDP / UPnP etc.)?
  6. 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?
  7. Performance
    • try to get rid of using the bearer classes (and thread) by default, they are seldomly used (this would imply deprecating QNetworkAccessManager::networkAccessible())
  8. New in 5.8
    • HTTP/2
    • OAuth 1+2
  9. Providing widgets for QtNetwork
    • What to do about dependencies?
    • What should we include?
    • URLBar widget (danimo)
    • SSL configuration widget (rich)
    • What about a certificate dialog?
Retrieved from "https://wiki-qt-io-staging.herokuapp.com/index.php?title=Qt_Network_Workshop_2016&oldid=28135"