bug-wget
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-wget] About GSoC project: Support QUIC Protocol


From: Jay Bhavsar
Subject: [Bug-wget] About GSoC project: Support QUIC Protocol
Date: Fri, 9 Mar 2018 01:12:08 +0530

Hello Community!

I'm Jay Bhavsar, a final year student from LDCE, Ahmedabd, India. I find
this project very interesting and want to contribute further. I have made a
few contributions and explored code base a little on my own. I am
considering to apply for "Support QUIC Protocol". I have read this
<https://docs.google.com/document/d/1WJvyZflAO2pq77yOLbp9NsGjC1CHetAXV8I0fQe-B_U/edit>
specification, and understood most of it. And I'm planning to read further
specifications from official site <https://quicwg.github.io/>.

However, I have few questions about this project and I hope someone can
help me out.

1.When should QUIC be used?
I think all the requests should use TCP by default unless explicitly told
to use QUIC by some flag. If we get  "Alternate-Protocol: 123:quic" in
response header we should inform the user, close TCP connection and use
QUIC instead. This behavior should modifiable with a flag. Is this the
right approach?

2.How should it be implemented?
I feel it should be implemented as part of libwget as family of functions
(like TCP). Any suggestions?

3.What should be the expected results?
It isn't specified formally on wiki page, but I think we should be able to
communicate with HTTP using QUIC protocol. Is there something more to it?

4. And finally, Am I good enough? (What are the prerequisites?)
I'm mostly familiar with C programming. I have some basic experience in
socket programming as well. That being said, I have never implemented a C
library. I have used many, modified some, but implemented none. Will I be
able to handle this project?

I was also considering "JWT and JOSE support" project. Will it suit my
skill set better? (I'm reading its official docs)


Thanks. I'm really excited to be part of the community!

Regards,
Jay Bhavsar.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]