Henry Popp

Thanks for the request! Perhaps someone might be interested in taking it up as a new library? The Pigeon 2.0 release candidates support custom push adapters for use-cases just like...

Thats probably it exactly. If you notice in the def block directly above: ```elixir # nil settings means use default def process(%Frame.Settings{ack: false, settings: nil}, state) do %{flow_control: flow, config:...

Should be fixed with `v0.4.4`. Let me know if it crops up again.

## Tentative API ```elixir Kadabra.get("https://http2.golang.org/") Kadabra.post("https://http2.golang.org/", body: "whatever", params: "yeah") Kadabra.request(%Kadabra.Request{...}) # Shouldn't be directly used in the majority of cases # Use a specific connection pid = Kadabra.open("https://http2.golang.org/", ssl:...

I suspect it's probably an issue with your production environment, but it'd be impossible for me to say without knowing more about your setup. Kadabra uses erlang's `:ssl` module under...

Receiving split headers works great, but currently none of the other features are supported. Up to now Kadabra has been used almost exclusively for Pigeon, but it is worth finally...

Latest PR merge adds a couple requested features. Streams and frames have been massively overhauled using the new `:gen_statem`. Now requires Elixir 1.4 and OTP 19 or later. Push promises...

Go figure, I guess they either moved it or turned it off. I'll have to look up a new solution for testing. Thanks for the heads up!

Hey, I appreciate the PR! I think you're the first to independently build an integration using the new adapter style. Perhaps this might be best published as its own package?...

Thanks for the suggestion! The empty row was an oversight on my part, I’d be fine having it return empty headers by default. You’re more than welcome to open a...