register multiple setup functions #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
May 7, 2013 17:35
0.4 is not available anymore
rewrite setup to register a function instead of setting it directly
Register shutdown functions for bolts, as counterpart to SetupFunc.
|
Thanks for your feedback. |
velvia
added a commit
that referenced
this pull request
May 22, 2013
register multiple setup functions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Instead of setting a setup function you can register one, which does not override the one, that was previously registered.
Provide a ShutdownFunc trait, which acts as counterpart.
So it is possible to have a resource in a provider trait, which has SetupFunc and ShutdownFunc as selftype and which itself could be mixed into a bolt to provide its resource.