WIP - Proxy classes - IProxy, TComponentProxy, TModuleProxy, TCacheProxy, TDataSourceConfigProxy - #1157
Draft
belisoful wants to merge 1 commit into
Draft
WIP - Proxy classes - IProxy, TComponentProxy, TModuleProxy, TCacheProxy, TDataSourceConfigProxy#1157belisoful wants to merge 1 commit into
belisoful wants to merge 1 commit into
Conversation
…DataSourceConfigProxy
Member
Author
|
These may be needed for Multi-application mode regarding truly global singletons like THttpRequest. |
belisoful
changed the title
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
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.
This is a very interest set of classes.
I'm not the biggest fan of TModuleProxy, but Cache and Data Source Config Proxy would be extremely useful.
The proxy can be the primary and Backing can be changed on the fly for all modules linked to the Proxy rather than changing each one separately.
Also, a subclass of TModuleProxy could serve as a TLazyModule that gives out the lazy proxy, and when it gets called, it would load the lazy module and start calling it through the proxy.
Some interesting options.