Hi winterbe, your article is very good, it introduces the new features of Java 8 in detail, so I translate it into Chinese。Thank you!!!

Link：https://github.com/aalansehaiyang/java8-tutorial

你好，winterbe。你的文章写的真棒，里面详细介绍了Java 8新特性，我将它翻译成了中文。谢谢

链接地址：https://github.com/aalansehaiyang/java8-tutorial

Following tokio-rs/mio#928.

Generally speaking when changing from level to edge trigger you need to put read/write in a loop, because it could that after a call to read/write another one is ready once the first one is done.

TcpConnection needs to basically call read in a loop here: https://github.com/Genymobile/gnirehtet/blob/2bf8a3cfbe2168031897b8f917c088fe6d4771

Is your feature request related to a problem? Please describe.

Configuration options are not documented on the web site.

Describe the solution you'd like

I need to look at the code (i.e. the *Config classes) or at the Javadoc in order to determine the configuration options. I'd like to have it documented on the website and to be sure that the configuration options match whatever

The current javadoc reads:

* The uri of the request message.
* Uri query parameters are available via {@link #parameter(String)} and {@link #parameters()}.
* Uri pathArgs are available in {@link RequestContext}.

Some details that are unspecified:

• Does the uri contain the scheme of the incoming request?
• Does it contain the authority?
• How does it relate to Route.uri?
• What are the

@OvermindDL1 says "I think all the tests should be adjusted to take the integer on the program parameters or an environment variable or something. That would both prevent such optimizations and would allow for easily CI'd consistency checks."

I'm looking for any documentation that provides more information or recommendations on managing the Nakadi platform in a production environment.

• High-available setup
• Capacity management
• Backup/restore strategies
• Release management (upgrade strategy)

Is there any community forum to discuss the Nakadi platform?

I went through documentations to try picking up this library and I think there are several things can be improved:

Major:

• Add a reading order to the documentation.
  Documentation right now are fragmented and all over the place, as a beginner after Quick Start, i dont know which one I should be reading next.
  Perhaps a proper table of content with number ordering would be nice