<div dir="ltr">Hey Loïc,<div><br></div><div>Once I included MASTER for cowlib, things started working. Thanks, Pablo! It looks like MASTER in Gun which has the HTTP/2 code is using v1.3 of Cowlib (in the rebar.config file) which does not seem to have the HTTP/2 code.</div><div><br></div><div>Thanks for all your hard work on these libraries!</div><div><br></div><div>Andrew</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 30, 2016 at 1:04 AM Loïc Hoguin <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I do not know if the people using Gun in production so far have tried<br>
the HTTP/2 support we currently have. Personally all I can say is that<br>
it works fine with Cowboy 2, but then again Cowboy 2 doesn't have flow<br>
control either at this time.<br>
<br>
Gun and Cowboy 2 are developed concurrently so they'll always be<br>
compatible. Other servers, I suppose it depends on how strict they<br>
implement flow control. Not aware of an issue yet, but would love some<br>
feedback on it.<br>
<br>
On 09/30/2016 09:46 AM, Andrew Berman wrote:<br>
> Hi Pablo,<br>
><br>
> Possibly that was the issue, I'll try again, but I do see a bunch of<br>
> TODOs in the gun code for HTTP/2, so it doesn't seem as ready for<br>
> production use as the Chatterbox client Derek mentioned.<br>
><br>
> Thanks,<br>
><br>
> Andrew<br>
><br>
> On Thu, Sep 29, 2016 at 7:45 PM Pablo Polvorin<br>
> <<a href="mailto:pablo.polvorin@process-one.net" target="_blank">pablo.polvorin@process-one.net</a> <mailto:<a href="mailto:pablo.polvorin@process-one.net" target="_blank">pablo.polvorin@process-one.net</a>>><br>
> wrote:<br>
><br>
> Hi Andrew, maybe the problem was with dependencies?. We are<br>
> evaluating gun as well, and got an error on the first try but the<br>
> problem was that the version of cowlib we were using didn't include<br>
> the latests http2 changes. Switching to cowlib master solved that.<br>
> We aren't using it on production yet, and there are parts missing<br>
> -like flow control- , but if our experience counts, so far it seems<br>
> to be good enough for our use case (we need to interact with only one<br>
> http/2 server implementation, on a fairly controlled way).<br>
><br>
><br>
><br>
><br>
> On 29 September 2016 at 20:12, Andrew Berman <<a href="mailto:rexxe98@gmail.com" target="_blank">rexxe98@gmail.com</a><br>
> <mailto:<a href="mailto:rexxe98@gmail.com" target="_blank">rexxe98@gmail.com</a>>> wrote:<br>
> > Is there a production ready HTTP/2 client available in Erlang? I've<br>
> > searched and only found Gun to have some support for HTTP/2, but<br>
> when I<br>
> > tried to use it I got an error, and it looks like it's not quite<br>
> ready for<br>
> > primetime (correct me if I'm wrong, Loïc).<br>
> ><br>
> > Thanks!<br>
> ><br>
> > Andrew<br>
> ><br>
> > _______________________________________________<br>
> > erlang-questions mailing list<br>
> > <a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a> <mailto:<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a>><br>
> > <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Pablo Polvorin<br>
> ProcessOne<br>
><br>
><br>
><br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
><br>
<br>
--<br>
Loïc Hoguin<br>
<a href="http://ninenines.eu" rel="noreferrer" target="_blank">http://ninenines.eu</a><br>
Author of The Erlanger Playbook,<br>
A book about software development using Erlang<br>
</blockquote></div>