A goroutine making each request, passing in the http.Client should work.
Something like http://blog.narenarya.in/concurrent-http-in-go.html
On Wed, 2 Aug 2017 at 18:58 wrote:
> Parallel in the sense of HTTP/2 multiplexing, i.e. sending the next
> request without having to wait for the reply of
On Thursday, 13 July 2017 15:56:27 UTC+1, pala.d...@gmail.com wrote:
>
> Hello, I'm trying to understand how to write an HTTP client using the
> standard HTTP package and which takes advantage of HTTP/2 multiplexing
> (i.e. send many requests "in parallel" using the same TCP connection).
>
> On
On Thursday, 13 July 2017 04:56:25 UTC+1, Ian Lance Taylor wrote:
>
> On Wed, Jul 12, 2017 at 8:56 AM, James Abley > wrote:
> >
> > Labels for clarity:
> >
> > 1. goroutine 1 spawns goroutine 2 to read from Oregon, and spawns
> goroutine
> > 3
On Wednesday, 12 July 2017 13:57:16 UTC+1, Ian Lance Taylor wrote:
>
> On Wed, Jul 12, 2017 at 12:28 AM, >
> wrote:
> >
> > On Wednesday, 12 July 2017 04:44:43 UTC+1, Ian Lance Taylor wrote:
> >>
> >> On Tue, Jul 11, 2017 at 12:27 PM, wrote:
> >> >
> >> > This caught me out recently; th
On Wednesday, 12 July 2017 04:44:43 UTC+1, Ian Lance Taylor wrote:
>
> On Tue, Jul 11, 2017 at 12:27 PM, >
> wrote:
> >
> > This caught me out recently; there's definitely a gap in my
> understanding as
> > to how select works. Maybe it's caught other people out too?
> >
> > For one of my
This caught me out recently; there's definitely a gap in my understanding
as to how select works. Maybe it's caught other people out too?
For one of my clients, I'd written an application that would try to read
data from a backend. There were multiple instances of this backend (say one
in Orego
