You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is only one resolution cache and it is located in root container. OpenScope does not create its own.
This inflicts number of problems with scope (name) drpendent services, e.g. we need different implementations for scoped and singleton service, or between different named scopes. To solve it we fallback to more powerful but slow context aware Resolve(...Request preResolveParent,...) and keyed resolution cache.
The new idea is to have cache-like structure with the root cache and multiple scope caches. Each scope cache will contain delegates resolved in scope, and the cache will be identifed by whole nested scopes route, e.g. "/*/*/name/*". Then OpenScope will set the matching scope cache as default to look for, or will create a new scope cache for the first time.
The text was updated successfully, but these errors were encountered:
dadhi
changed the title
Consider hierarchical route-like resolution cache for default dekegates
Consider hierarchical route-like resolution cache for default delegates
Aug 19, 2018
Currently there is only one resolution cache and it is located in root container.
OpenScope
does not create its own.This inflicts number of problems with scope (name) drpendent services, e.g. we need different implementations for scoped and singleton service, or between different named scopes. To solve it we fallback to more powerful but slow context aware
Resolve(...Request preResolveParent,...)
and keyed resolution cache.The new idea is to have cache-like structure with the root cache and multiple scope caches. Each scope cache will contain delegates resolved in scope, and the cache will be identifed by whole nested scopes route, e.g.
"/*/*/name/*"
. ThenOpenScope
will set the matching scope cache as default to look for, or will create a new scope cache for the first time.The text was updated successfully, but these errors were encountered: