Add http2.dart and prepare for 1.0

[sigurdm]

This fixes dart-lang/http#1352 and dart-lang/http#1344

[sigurdm]

cc @mkustermann

[mit-mit]

Maybe add a line here with * Graduate package to 1.0.

[sigurdm]

Done

[mkustermann]

LGTM - Though notice that there is still no stream prioritization implementation (afaik)

[sigurdm]

Right. I am not sure what that would entail.
Would you consider that needed for a 1.0?
Would it be a breaking change to add it?

[jonasfj]

Though notice that there is still no stream prioritization implementation (afaik)

@mkustermann, is there any reason to believe this can't be implemented without breaking the public API?

I'm not sure how it would look, but really that's the only question before going 1.0.

[kevmoo]

Since this is a breaking change release, could we remove one of the top-level libraries? Or both? Could we just have http2.dart?

[mkustermann]

For some background: It's called transport.dart because it's implementing the transport mechanism. It doesn't implement application-level things (like making a http get request, ...)

I'm not sure how it would look, but really that's the only question before going 1.0.

If we don't expose priorities to the user, it can be implemented without breaking changes, yes.

[sigurdm]

Since this is a breaking change release, could we remove one of the top-level libraries? Or both? Could we just have http2.dart?

I don't think we should make breaking changes just because we can.
I prefer to keep the existing library around.

Also, looking forward http2.dart could expose more high-level abstractions...

[sigurdm]

When we implement priorities we can go to 2.0 if it turns out to be best done in a breaking fashion.

I think the library as it is now implements a meaningful and useful subset of http2, and it is fair to give it a stable version number indicating that users can feel comfortable relying on it.