Open
Conversation
added 13 commits
June 11, 2014 16:24
- ProcessRPCClient auto-updates to ExchangeNameService for to_name if not one already - ION Service Processes listening on ExchangeNameServices
Member
|
👍 Very nicely done. I'm waiting for the builder results, but this is ready to go to pyon thereafter |
added 6 commits
June 12, 2014 12:24
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Several underlying changes to pyon.net/pyon.ion.exchange infrastructure to more broadly support ExchangeObjects. Endpoints automatically upgrade to using ExchangeObjects when the ability becomes available. Events also updated.
PR for review / letting buildbot do it's thing. I've tested rather extensively locally but as this is a very substantial, sweeping change, there are likely going to be ripples.