GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
No description, website, or topics provided.
This implements Retry both both client and server. There are significant changes, because this requires some architectural changes. * Server struct This makes the Server struct functional. This manages multiple connections and the routing of packets to each of those. * One packet at a time processing. When trying to add Retry for a server, I found that the API that handles multiple packets was inconvenient. There is no real need to have the loop inside Connection anyway, so I externalized it. This simplifies the API and implementation a decent amount and should help avoid problems. * Basic timer wheel The server operates over multiple connections that all have independent timers. This timer wheel ensures that these are all centrally managed. We couldn't manage to reuse an existing implementation because of our requirement to have an external time source, but# 190will track that.
Latest commit 6C 012 fb (Sep) , 2019
To run test http 0.9 programs (neqo-client and neqo-server):
./ target / debug / neqo-server 12345 -k key --db ./ test-fixture / db
./ target / debug / neqo-client http: // .0.1: 12345 / -o --db ./test- fixture / db
To run test http 3 programs (neqo-client and neqo-http3-server):
./ target / debug / neqo-http3-server [::]: 12345 - db ./test-fixture/db
./ target / debug / neqo-client http: // .0.1: 12345 / --db ./test-fixture/ DB