QUIC transport? #1078
Labels
Comments
|
Hi I saw this issue as a gsoc idea. I am interested in doing this. so I would like to know in detail about the issue. As I understood QUIC codec for netty is the requirement. Can you suggest any tips to get started |
|
@anuradhacse great, this is going to be a cool GSOC project! |
|
So as I understood I have to write a QUIC codec for Netty so that it can be
used in linkerd. I briefly went through the draft specification document of
QUIC protocol and looked at Netty codec. so do you have any suggestion on
how to proceed on this project.
…On 11 March 2017 at 03:13, William Morgan ***@***.***> wrote:
@anuradhacse <https://github.com/anuradhacse> great, this is going to be
a cool GSOC project!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1078 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALn-Y-n2Vo0JAT1sOoK71gNC1S3jmJYWks5rkcQUgaJpZM4MDoxL>
.
|
Tim-Brooks
pushed a commit
to Tim-Brooks/linkerd
that referenced
this issue
Dec 20, 2018
…inkerd#1078) * Display font-awesome icons no matter what URL is originally loaded The URLs in the dashboard need to be relative. Unfortunately, this means that if you load something that isn't the base route ... font-awesome icons look broken. There's no real way to solve this from within webpack (or the web server without some work). Instead, just load font-awesome from a CDN as there's no real benefit we get from including it in the bundle. Fixes linkerd#1019. * Moving font-awesome to styles
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It doesn't appear that anyone has written a QUIC transport for netty. It would be extremely appealing to have a such a transport available in linkerd.
The text was updated successfully, but these errors were encountered: