Implementation of StorageProvider events #37
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to support things like S3 Sync, we need a simple event system to be able to send events from one part of Silo to another, allowing for the fact that StorageProviders may have been wrapped / changed etc by the consumer of Silo.
Example:
data := sources.NewMemory(1024*1024)
// In Silo
storage.AddEventListener(data, "sync_start", callback)
// Silo user code
metrics := modules.NewMetrics(data)
silo.DoSomethingWith(metrics)
// Back to silo
returned_data := storage.SendEvent(metrics, ….)
In this example, the callback registered against the storage "data" should get called when the event is triggered against metrics.