REQ-201 One ESME in Many Clusters #240
Open
+134
−55
Conversation
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
commit aa38359688a0940004bd2bfb37b2a371c90fb86b Author: Adam Gorak <[email protected]> Date: Fri Jul 7 16:22:04 2017 +0200 Adaptation for 1-esme. commit 21aab8c0449b69e668bd2dd1ff7cf2b0f870a51e Author: Adam Gorak <[email protected]> Date: Fri Jul 7 00:20:55 2017 +0200 2 important fixes. commit a6d457bc3df5b9ef44ef4011407a1a4803f614f8 Author: Adam Gorak <[email protected]> Date: Wed Jul 5 01:04:18 2017 +0200 Let us try with this 1 ESME in many clusters. commit 9e49024930a66fc1d27c92817d3ef0b287021708 Author: Adam Gorak <[email protected]> Date: Thu May 11 02:23:29 2017 +0200 Trying to prepare for handling of 1 ESME in many clusters. Conflicts: pom.xml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi,
this PR is related with: RestComm/smpp-extensions#25
Basically, if 1 ESME, can potentially be in more than 1 cluster, when when searching for the original message we need to check all the clusters, the ESME is declared in.
Please review together with the related PR and let me know your feedback - so that we can discuss it further.
Regards,
adam