level that is what all web
> server implementations do - they read from the socket directly.
>
> On Feb 11, 2024, at 7:54 PM, 'Rohit Roy Chowdhury' via golang-nuts <
> golan...@googlegroups.com> wrote:
>
> As stated earlier, objective is to create a web server without using
> n
wn.
>
> On Feb 11, 2024, at 5:36 PM, 'Rohit Roy Chowdhury' via golang-nuts <
> golan...@googlegroups.com> wrote:
>
> Yes I got it but I want to know if *reader.ReadString("\n")* is supposed
> to throw *io.EOF* rather than blocking for next request in the connecti
that client. Http2 complicates this a bit as it has multiple
> connections over a single tcp connection.
>
> On Feb 11, 2024, at 4:22 PM, 'Rohit Roy Chowdhury' via golang-nuts <
> golan...@googlegroups.com> wrote:
>
> I got your point. But *reader.ReadString('\n')* does
I got your point. But *reader.ReadString('\n')* does not block like you
said. After a request gets parsed, from the next iteration it keeps on
emitting *io.EOF *until next request arrives.
On Sunday, February 11, 2024 at 9:37:43 AM UTC-8 Brian Candler wrote:
> You're thinking backwards. "Long
