Handling GoAway error in xitca-client

[basic-bgnr]

Hi!. Thanks for this great project.
I am currently trying to replace reqwest in my pet-project with xitca-client.
I managed to get it working but there were several hiccups.

Problem:
I'm getting H2 GOAWAY error whenever the client is suspended more than 60 secs. I can't handle specific GOAWAY error because it isn't exposed as pub here (is this intended? Are we supposed to handle H2 error or it's the responsibility of xitca-client ?)

Minor problem:
I tried changing the keep_alive_idle time in ClientBuilder but it wouldn't work. The docs

xitca-web/client/src/builder.rs

Line 338 in 1d46f9a

/// Default to 10 minutes.

says default idle time is 10 min but its only 1 min

xitca-web/client/src/builder.rs

Line 46 in 1d46f9a

keep_alive_idle: Duration::from_secs(60),

. Maybe an extra zero is missing here.

[fakeshadow]

It's reasonable to expose http2 error types as public types. PR is welcomed for exposing them through xitca_client::error::h2. The specific error types can either be using foreign types through h2 crate or re-export from xitca-client

keep-alive timers are not enabled for http/2 client right now. The client will accept server's configuration including timer. It's likely the server side decide h2 connection only live as long as 60 secs and the go away frame is a normal way of telling client to gracefully shutdown connection.

[basic-bgnr]

@fakeshadow xitca_client::error::Error::H2 is a wrapper for xitca_client:h2::error::Error::H2, which in-turn is a wrapper for h2::Error from h2 crate.
since h2 mod inside xitca_client is private, simply exporting h2 mod as pub would enable user to handle xitca_client_error::Error::H2 error.
Is there any reason to keep h1, h2 or h3 mod as private ?