Very good question. I don't know, and obviously it would be preferable to understand what's really going on. From a distance the best I can do is guess.
If you did try it with multiple clients and it fixes the problem then that should point you in the right direction. If not, try Go's profiler, different machines, different operating systems, different LANs, etc. It could even be a problem on the server side -- the app or Apache or the OS's network stack could have a buffer issue or some resource not being freed quickly enough -- who knows? Maybe create a simple mock backend and run it locally and hammer it. If you can reproduce the problem that way, that would be very telling. -- 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. For more options, visit https://groups.google.com/d/optout.
