
|
If you were logged in you would be able to see more operations.
|
Google issue summary
|
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
5.1 M2
|
|
|
Time Tracking:
|
|
Original Estimate:
|
4 hours
|
|
|
Remaining Estimate:
|
4 hours
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
|
The idea is to have an simple cache key for documentModels.
This cacheKey will be helpful at least for managing invalidation of page fragment cached with s:cache.
<s:cache key="#{currentDocument.cacheKey}"> ... </s:cache>
For a basic implementation, this cacheKey could be generated with :
documentId + sessionId + timeStamp
documentId = uuid
sessionId = core session id (isolate security problem at least for now)
timeStamp : time stamp of the last write operation in the core
The timeStamp generation could be added to the dublinCore event listener.
|
|
Description
|
The idea is to have an simple cache key for documentModels.
This cacheKey will be helpful at least for managing invalidation of page fragment cached with s:cache.
<s:cache key="#{currentDocument.cacheKey}"> ... </s:cache>
For a basic implementation, this cacheKey could be generated with :
documentId + sessionId + timeStamp
documentId = uuid
sessionId = core session id (isolate security problem at least for now)
timeStamp : time stamp of the last write operation in the core
The timeStamp generation could be added to the dublinCore event listener.
|
Show » |
|