Skip to content
This repository was archived by the owner on Jan 13, 2021. It is now read-only.

Commit bfffb42

Browse files
committed
FAQs.
1 parent 4fdd6de commit bfffb42

File tree

2 files changed

+65
-0
lines changed

2 files changed

+65
-0
lines changed

docs/source/faq.rst

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
.. _faq:
2+
3+
Frequently Asked Questions
4+
==========================
5+
6+
``hyper`` is a project that's under active development, and is in early alpha.
7+
As a result, there are plenty of rough edges and bugs. This section of the
8+
documentation attempts to address some of your likely questions.
9+
10+
If you find there is no answer to your question in this list, please send me
11+
an email. My email address can be found `on my GitHub profile page`_.
12+
13+
.. _on my GitHub profile page: https://github.com/Lukasa
14+
15+
What version of the HTTP/2.0 draft specification does ``hyper`` support?
16+
------------------------------------------------------------------------
17+
18+
Currently, ``hyper`` supports version 9 of the HTTP/2.0 draft specification,
19+
and version 5 of the HPACK draft specification. ``hyper`` will be updated to
20+
keep up with the HTTP/2.0 draft specifications as they progress.
21+
22+
Does ``hyper`` support HTTP/2.0 flow control?
23+
---------------------------------------------
24+
25+
It should! If you find it doesn't, that's a bug: please report it on GitHub.
26+
27+
Does ``hyper`` support Server Push?
28+
-----------------------------------
29+
30+
No, and I don't think it ever will directly. Support for Server Push
31+
effectively *mandates* a multithreaded or event-loop based programming style,
32+
which is incompatible with most current Python HTTP code. For that reason,
33+
``hyper``'s default API is unlikely to ever allow Server Push.
34+
35+
However, there's no reason the underlying framing and stream layers couldn't
36+
support it. If ``hyper`` ever grows a server implementation or a fully
37+
event-loop based implementation, I'll revisit the decision not to support
38+
Server Push.
39+
40+
I hit a bug! What should I do?
41+
------------------------------
42+
43+
Please tell me about it using the GitHub page for the project, here_, by filing
44+
an issue. There will definitely be bugs as ``hyper`` is very new, and reporting
45+
them is the fastest way to get them fixed.
46+
47+
When you report them, please follow the contribution guidelines in the README.
48+
It'll make it a lot easier for me to fix the problem.
49+
50+
.. _here: https://github.com/Lukasa/hyper
51+
52+
Updates
53+
-------
54+
55+
Further questions will be added here over time. Please check back regularly.

docs/source/index.rst

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,16 @@ The quickstart documentation will help get you going with ``hyper``.
4545

4646
quickstart
4747

48+
Frequently Asked Questions
49+
--------------------------
50+
51+
Got a question? I might have answered it already! Take a look.
52+
53+
.. toctree::
54+
:maxdepth: 2
55+
56+
faq
57+
4858
API Documentation
4959
-----------------
5060

0 commit comments

Comments
 (0)