Still an enthusiastic Go semi-novice but I was surprised that Grav offers both a non-blocking and a blocking message receive. I would have thought that the paradigm in Go would have been to offer only the blocking receive and to run that in a goroutine and then sync over a channel to avoid callbacks :)
Would love to know why both are offered and where you've used the async receive...
Still an enthusiastic Go semi-novice but I was surprised that Grav offers both a non-blocking and a blocking message receive. I would have thought that the paradigm in Go would have been to offer only the blocking receive and to run that in a goroutine and then sync over a channel to avoid callbacks :)
Would love to know why both are offered and where you've used the async receive...