Feature request: KAS processing threshold provided by AccountLimit #22
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.
Starting with KIM 1.5 specification, the current threshold from which a KIM-Clientmodul processes received/large mail data by the defined 'KAS process' is fixed to 15 MiB. Any KIM mail smaller than 15 MiB must be processed 'normally'/fully by TI-Konnektor.
To mitigate the known performance & memory issues of the TI-Konnektor, it might be benefitial to allow a smaller, by all means, variable threshold from which the KIM-Clientmodul uses the 'KAS process' instead of processing large amounts of data by a TI-Konnektor.
Solution:
Extend AccountLimit by a property 'kasMailSizeThreshold', which allows a threshold between 1 MiB and 15 MiB (default). Currently any KIM-Clientmodul implementing KIM 1.5 specification must request the AccountLimit before sending a message.
Advantage:
Disadvantage:
The KIM/KAS provider must decide/manage the threshold value, as the overall KAS performance and related storage management might be individual to each provider.