https://bugzilla.wikimedia.org/show_bug.cgi?id=18464
--- Comment #1 from Michael Dale <[email protected]> 2009-04-14 19:16:49 UTC --- some thoughts.. the fact that we have wiki pages for user language / msg updates means we have to pull the revision id of the latest updated msg text from the javascript we are including before we write out the unique id for the javascript grouped request... likewise for articles I need to grab the latest revision id from all of wiki page javascript includes and them hash that with the svn version id of the actual files used to create the unique request identifier. How does the system insure that once the squid version of a resource is "purged" all the requests that happen in the mean time while the resource is being updated don't hit un-cached version of things? hmm need to think about how that would work in this context .. I guess it should render it out when its rendering out when the head of the page that points to that unique identifier / script group request. So its just part of the page rendering process that can take ~ seconds ~ so when the user gets a page with a new <script tag pointing to some grouped resource request that grouped resource request should already be rendered out and cached. Not sure if that completely solves the problem... more updates shortly. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
