Details
-
Improvement
-
Resolution: Fixed
-
High
-
5.0
-
Stetind Sprint 4, Stetind Sprint 5, Stetind Sprint 6
Description
Repository should not be aware of storage engine specifics. Awareness was added in: https://github.com/ezsystems/ezp-next/pull/145
Several problems on moving all traces of this to legacy storage layer:
- doing it without affecting performance
- we need main language information not available in storage without additional querying
- using SignalSlot for publishing aliases / plan for treating URL aliases as cache
- can we treat path_identification_string as cache?
What about simplified implementation eg. "location_2/location_5/location_42"?