How does Response.Write make sure that client can receive reponse-bytes immediately without Flush() opt ?

[stormgbs]

As described in the title. How does Response.Write make sure that client can receive reponse-bytes immediately without Flush() opt ?

[valyala]

There were two options for sending responses with fasthttp until today:

1. Via fasthttp.Server. The server automatically sends http response after user's code returns from the outer RequestHandler . See Server.serveConn implementation for details.
2. Via Response.Write call. In this case the caller must call bufio.Writer.Flush in order to make sure the response is sent to the client.

After the commit f8c0d95 yet another approach has been appeared for sending responses - using Response.WriteTo.

[stormgbs]

Thank @valyala , fasthttp is owesome:) . I am writeing a http router(http reverse proxy) based on fasthttp, I modified some fasthttp code, so that I can copy response bytes from lower conn(proxy<-->backend server) to upper-conn(client <--> proxy) directly.