[MGNLADVCACHE-41] Don't use personalised paths Created: 11/Feb/15 Updated: 16/Feb/15 Resolved: 16/Feb/15 |
|
| Status: | Closed |
| Project: | Advanced Cache |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Roman Kovařík |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | m2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Epic Link: | DPC |
| Description |
|
When rendering a page for the first time, dynamic fragments path are generated and such page is saved into cache. |
| Comments |
| Comment by Roman Kovařík [ 16/Feb/15 ] |
|
We will cache variants instead of creating dynamic fragments without personalised paths. |