Closed Bug 747154 Opened 12 years ago Closed 12 years ago

kumascript: Improve caching for kuma -> kumascript

Categories

(developer.mozilla.org Graveyard :: Editing, defect, P2)

Product:
developer.mozilla.org Graveyard
Component:
Editing
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: lorchard, Unassigned)

References

Details

(Whiteboard: u=developer c=wiki s=2012-05-22 p=2) 

There is response caching in kumascript for requests from kuma. It also handles 304 Not Modified responses to conditional GET.

However, this mechanism uses local memory, rather than memcache. So, multiple kumascript processes have separate caches. That means the caching is much less effective than if it were shared between all kumascript processes
Blocks: 659364
Whiteboard: u=contributor c=wiki s=2012-05-22
Whiteboard: u=contributor c=wiki s=2012-05-22 → u=contributor c=wiki
Hmm, actually, this has been addressed here:

https://github.com/mozilla/kumascript/commit/f05d343b04005d2bb9e688ca7d72130535e380c6

I appear to have snuck the fix in along with closing another caching bug.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: u=contributor c=wiki → u=developer c=wiki s=2012-05-22 p=2
Blocks: 710728
No longer blocks: 659364
Priority: -- → P2
Version: Kuma → unspecified
Component: Docs Platform → Editing
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.