[erlang-questions] HTTP/2 client

[Loïc Hoguin]

My bad, the deps seem incorrect indeed. Thanks for the info!

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

-- 
Loïc Hoguin
http://ninenines.eu
Author of The Erlanger Playbook,
A book about software development using Erlang