allow custom callback for checking recv messages - #14
Open
ptitdoc wants to merge 1 commit into
Open
Conversation
this allow writing special cases such as diameter apps that answer to multiple names/aliases, specific logging of recv messages, or implementing diameter messages proxying.
Author
|
Hello, Are you interrested by this commit ? The goal for me is to write a diameter proxy. I have working code but I don't really like it, I can publish it along anyway if you want it for reference. |
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
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 allow custom use cases for bromelia such as diameter apps that answer to multiple names/aliases, specific logging of recv messages, or implementing diameter messages proxying.
The simplest use case it is to actually disable node recv message (which I use for a diameter proxy as I don't care about the destination node, I just forward messages to the next peer):