-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Working ZeroMQ transport. #80
Merged
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
…or Dynamic Topology.
…ommit supports running all Mps in every node in a distributed manner. This allows application deployment on a cloud environment to be completely homogeneous.
…op' to 'shutdown.' Better javadocs the Receiver/Sender interfaces. This was for better handling of clients that get shut down from in the TcpTransport which also had changes. Added some trace logging to the main Dempsy orchestrator class. Small enhancement to the handling of errors when calls are made on a stopped container.
… tasks to finish. This provides a cleaner shutdown but may add delay. There are tests that periodically fail if this is not the case.
…. Also some tests have been fortified.
… files. Also better data-hiding in the InstanceWrapper.
…. Also created a way to override the cluster check in the main integration tests but defaulted it to the current behavior.
…o this the stopping of a session would result in callbacks on the session that was being stopped. That behavior is odd. The FIRST thing that should happen when a session is stopped is that it will not longer receive callbacks or be able to participate in the ClusterInfo management. This changes make this the case.
… hardcore but limits certain transports that are used.
…tions made to the code.
…corrects the DefaultDempsyExecutor and notes this fact in the javadoc of the DempsyExecutor.
…er is shutting down. This fixes that on the BlockingQueueAdaptor.
…te out the resusable pieces that support homogeneous deployment for use with 0mq.
…sn't waiting long enough for the cluster to stabalize and data to start coming through.
… a collection where before it used reflection to see what was passed.
…hat provides for multiple Nodes running within a single Dempsy instance.
…the DefaultDempsyExecutor imlpementation.
jimfcarroll
pushed a commit
that referenced
this pull request
Mar 18, 2013
Working ZeroMQ transport.
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.
This is a change required by the Dempsy-addons ZeroMQ PR here Dempsy/dempsy-addons#1