This is not true. The synchronous requirements are based on higher level protocol requirements. You can just as easily do async with Reader and Writer. Eg. The client can send multiple requests and the server could respond to these out of order (I.e the response contains the request id) or not respond at all. You might want to look at using gRPC which will help you understand the model better. On Aug 11, 2024, at 1:44 PM, 'lijh8' via golang-nuts <golang-nuts@googlegroups.com> wrote: -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/678FE9AE-3AD5-436E-831E-ECF7810ABB80%40ix.netcom.com. |
- [go-nuts] Order of calls to conn.Read and conn.Wri... 'lijh8' via golang-nuts
- Re: [go-nuts] Order of calls to conn.Read and... Robert Engels
- Re: [go-nuts] Order of calls to conn.Read... Robert Engels
- Re: [go-nuts] Order of calls to conn.... 'lijh8' via golang-nuts
- Re: [go-nuts] Order of calls to c... 'lijh8' via golang-nuts