2010/7/24 Platonides <[email protected]>:
> Your answer is even more confusing.
> You can split the html pages in the wiki in two pieces: the content (the
> part that changes by editing the wiki source) and the chrome (anything
> else) that comes from the skin (sidebar, edit tabs, portlets...)
>
> For users, the skin is not cached, it is generated on the fly. Whereas
> for anonymous users, it is cached as a static page in the squids (this
> is the reason wmf sites don't show p-personal for anons, so that all
> anonymous users share a single cache).
>
> If the CSS classes are always in the page, you can change censoring
> level by loading a different stylesheets (eg. alternate stylesheets)
> Similarly, it could be handled by JavaScript and personal rules stored
> in localstorage.
>
> It's probably just there, but I don't see where your "cached but
> dynamic" goes into the structure.
>
What Neil probably meant was the CSS and JS files in the /skins
directory, which are static files and are cached aggressively.

Roan Kattouw (Catrope)

_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to