Ticket #42 (new task)
Provide decent caching in kauri template module
| Reported by: | jgou | Owned by: | bruno |
|---|---|---|---|
| Priority: | major | Milestone: | 0.5 |
| Component: | modules/kauri-template | Version: | trunk |
| Keywords: | Cc: |
Description
Caching now only works when using the standalone template engine (with file- en jarsources), not with kaurisources.
Make it work with or without kauri xml pipelines ?
Attachments
Change History
comment:3 follow-up: ↓ 4 Changed 4 years ago by bruno
As noted in the commit message of r545, there are still serious limitations, e.g. caching happens on an the module-local URI. If two different modules contain a file 'kms:/templates/index.html', then the first one called will be in the cache and will be used for both modules.
comment:4 in reply to: ↑ 3 Changed 3 years ago by jgou
- Milestone changed from 0.3 to 0.4
Replying to bruno:
As noted in the commit message of r545, there are still serious limitations, e.g. caching happens on an the module-local URI. If two different modules contain a file 'kms:/templates/index.html', then the first one called will be in the cache and will be used for both modules.
We should probably fix this by including the module URI since users are experiencing problems. See http://groups.google.com/group/kauri-discuss/browse_thread/thread/cdfd637537a61e82?hl=en
comment:5 Changed 3 years ago by bruno
The problem with cache conflicts on the same "module:" URI in different modules has been solved in r1304.
While thinking of it, it would also be good to normalize URIs before using them in the cache key (e.g. remove /./ and /../ things). Or maybe Restlet does that?
Bruno did some first improvements in r545 .