Md5 methodId instead of unsigned int counter #207
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.
related issue
General
I hacked together a simple solution (and cleaned up the underlying frame generation a little) for utilizing md5 generated hashes for message Ids, which allows to assign/distribute different messages across multiple endpoints inside 1:n (or n:n) topologic network.
it is more costly (traffic and computational), but allows a more flexible approach for different types of underlying transport networks. The current erpc implementation cannot safely distribute messages across different endpoints.
This is a proof of concept and should contain all the necessary changes (it's actually not that much) and the "important" is actually contained inside the
erpcgen
tool (which is basically a sandbox for 'somewhat questionable' code practices anyways, as far as I can tell) :)Stuff that should not be here
There are also some changes in here which are not part of the overall solution to the problem, but are there because the develop branch seems to have some "not building on my system" problems, mainly:
These can be cherry picked if necessary (or fixed in the actual develop branch)
TLDR