...
To use DSFIDs, a class needs to register itself so that it is known by the serialization framework. Many core classes register in DSFIDFactory
. The modules, mentioned before, register during their service loader discovery and initialization phase. Under some situations, however, Geode will require knowledge of the DSFID very early on during member startup. If a member receives a message with an unknown DSFID it will throw a DSFIDNotFoundException
. Without introducing module circular dependencies, there is no way for a module to register its required DSFIDs early enough to avoid this issue.
Anti-Goals
N/ANone identified.
Solution
The proposed solution includes introducing a Service Loader interface - DSFIDLoader
- which will allow DSFIDs to be automatically discovered and will be initialized as part of the static class initialization already existing in InternalDataSerializer
.
...
No backwards compatibility impact.
Prior Art
N/A
FAQ
Answers to questions you’ve commonly been asked after requesting comments for this proposalNone yet.
Errata
What are minor adjustments that had to be made to the proposal since it was approved?None yet.