In the current implementation, the memory provider will just loop through a map of messages once when there's a new Subscriber. This expands the MemoryProvider out, making it a little more consistent with the code style of the others (a constructor, actually doing stuff in the shutdown, etc), and adds some more queue-like functionality using some channels and goroutines.
In the current implementation, the memory provider will just loop through a map of messages once when there's a new Subscriber. This expands the MemoryProvider out, making it a little more consistent with the code style of the others (a constructor, actually doing stuff in the shutdown, etc), and adds some more queue-like functionality using some channels and goroutines.