Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add support for the QUIC protocol #22657

Closed
DartBot opened this issue Mar 4, 2015 · 9 comments
Closed

add support for the QUIC protocol #22657

DartBot opened this issue Mar 4, 2015 · 9 comments
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-not-planned Closed as we don't intend to take action on the reported issue library-io type-enhancement A request for a change that isn't a bug

Comments

@DartBot
Copy link

DartBot commented Mar 4, 2015

This issue was originally filed by @kgersen


http://www.chromium.org/quic

Would be nice to have that in DartVM.

@DartBot
Copy link
Author

DartBot commented Mar 4, 2015

This comment was originally written by @Emasoft


I agree. Dart should integrate the QUIC protocol in in the default framework.

@floitschG
Copy link
Contributor

Added Area-Library, Library-IO, Triaged labels.

@sgjesse
Copy link
Contributor

sgjesse commented Mar 6, 2015

There are currently no plans of implementing QUIC as part of dart:io. It should be possible to implement this as a package using UDP support in dart:io. If the UDP support is not sufficient for this then that is an issue we can try to address.


Added NotPlanned label.

@DartBot
Copy link
Author

DartBot commented Mar 6, 2015

This comment was originally written by @kgersen


let's say someone implement the QUIC protocol in a package using UDP support dart:io. Then , how can we use that protocol with the HTTPServer class for instance (or HTTPClient). Wouldn't we have to rewrite new HTTP classes above QUIC ?

It's very related to how the Dart team will implement HTTP/2 in issue #321504. If they do that by creating a way to 'plug' new protocols underneath the core HTTP classes then the community could contribute in the future to implement QUIC or other protocols.

@DartBot
Copy link
Author

DartBot commented Mar 6, 2015

This comment was originally written by @kgersen


HTTP/2 is issue #21504 not 321504

@DartBot DartBot added Type-Enhancement area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. library-io closed-not-planned Closed as we don't intend to take action on the reported issue labels Mar 6, 2015
@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed priority-unassigned labels Mar 1, 2016
@VladimirCores
Copy link

VladimirCores commented Aug 4, 2020

Does it means that development of HTTP/3 for Dart language is over?

@gargakshit
Copy link

Any updates on quic?

@iapicca
Copy link

iapicca commented Oct 20, 2020

@Kellykinyama12
Copy link

We have started a pure dart dtls implementation on this repo:

https://github.com/Kellykinyama12/dart-pure-dtls
The project can be repurposed to handle tls, as tls and dtls are similar. There is a lib\crypto.dart file that can handle cryptography issues

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-not-planned Closed as we don't intend to take action on the reported issue library-io type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

8 participants