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
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
# 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()) | ||
# Providing widgets for QtNetwork | # Providing widgets for QtNetwork | ||
#* What to do about dependencies? | #* What to do about dependencies? | ||
| Line 36: | Line 33: | ||
#* Identify use-cases | #* Identify use-cases | ||
== | == Presentations == | ||
# High-level design and structure of QtNetwork | # High-level design and structure of QtNetwork | ||
#* Rationale for the design. | #* Rationale for the design. | ||
# New in 5.8 | |||
#* HTTP/2 | |||
#* OAuth 1+2 | |||
Revision as of 12:02, 24 August 2016
Proposed Discussion Topics
- Redirection support
- Should it be on by default
- more configurable...
- The test server
- How can we get the image - should we replace / update it? The Vagrant solution?
- 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 - status update and roadmap
- What are the main use cases for QtNetwork: HTTP(S)?
- Are there new use cases for e.g. IoT (UDP / UPnP etc.)?
- Implement a generic REST(?) service to make it simple to interface with a Qt application?
- 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())
- 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?
- Should QtNetwork's design / architecture be modified?
- Is it outdated in any area?
- Could it be made redundant by using a 3rd party something?
- Providing more server support for QtNetwork
- QSslServer
- An HTTP server?
- Identify use-cases
Presentations
- High-level design and structure of QtNetwork
- Rationale for the design.
- New in 5.8
- HTTP/2
- OAuth 1+2