Safe for use from concurrent goroutines?

[carbocation]

Is the client safe for use from concurrent goroutines?

[sideshow]

Yes it it - It uses the underlying Transport which is safe for concurrent use by multiple goroutines. We are using it in production in this manner.

[carbocation]

I think it's worth mentioning this in the comments (for example, database/sql does so). I can create a pull request if that would be worthwhile.

[sideshow]

Great idea, yes please!

[sagarp-webonise]

To avoid fatal error of concurrent map read and write, are you using Push or PushWithContext? I am using this package and concurrent go routines trying to Push() notification always results with fatal error. Can you help me with sample example to avoid this fatal error?