QtCS2017 QtNetwork: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 25: | Line 25: | ||
* Not just QSslSocket the proxy engines as well | * Not just QSslSocket the proxy engines as well | ||
* CoAP is the some use case as Quic from Google | * CoAP is the some use case as Quic from Google | ||
* ( | * (Thiago) Add a way to watch a module | ||
* Testing: Network tests are working | * Testing: Network tests are working | ||
** Problems to access the network test server image | ** Problems to access the network test server image | ||
| Line 34: | Line 34: | ||
*** Remind the wiki page about how to write good network test. | *** Remind the wiki page about how to write good network test. | ||
* QtSSHServer | * QtSSHServer | ||
* Let's Encrypt API | |||
** Needed by HTTP and CoAP servers | |||
Latest revision as of 09:46, 10 October 2017
QtCore and Network team
Ideas/topics to discuss:
- HTTP server
- Present status
- Currently internal repository. Public repository requested.
- Present scope
- Use cases?
- Authentication
- Simple HTTP Server
- REST
- Server-side concurrency (limited). Green threads
- Internal testing. (Replace MiniHttpServer)
- Protocol support (HTTP / HTTPS / HTTP2 / WebSockets / Secure WebSockets / CoAP?)
- Improve JSON support
- Present status
- CoAP (needs DTLS)
- DTLS support (who can / will do what?)
- MQTT
- ZeroMQ
- Lack of reviews
- Contribution is not easy
- Permanent storage for network?
- It comes from previous network team
- Not just QSslSocket the proxy engines as well
- CoAP is the some use case as Quic from Google
- (Thiago) Add a way to watch a module
- Testing: Network tests are working
- Problems to access the network test server image
- It's old
- Update is not working
- Improve
- Tests blacklisted without investigation. Email somebody to take a look to the test.
- Remind the wiki page about how to write good network test.
- Problems to access the network test server image
- QtSSHServer
- Let's Encrypt API
- Needed by HTTP and CoAP servers