I'm not interested in writing an entire explanation for you on how cache
manifests work and their faults when you could simply do a web search
for one of the many existing tutorials.
The issues with using cache manifests to try and do this should be
perfectly understandable once someone understands how cache manifests work.
They are unusable for this technique.
And Ori has already explained the advantage of being able to have
modules cached separately.

You're basically suggesting we try to make orange juice out of apples
instead of oranges.

~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]

On 2013-11-08 12:46 AM, John Erling Blad wrote:
> That is a statement, not an explanation.
> Please provide a valid explanation why you want to do this.
> John
>
> On Thu, Nov 7, 2013 at 9:35 AM, Daniel Friesen
> <dan...@nadir-seen-fire.com> wrote:
>> Cache manifests are extremely inflexible. The HTTP caching we already
>> have is more flexible than cache manifests. So cache manifests won't
>> help make any improvements.
>>
>> ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
>>
>> On 2013-11-07 12:19 AM, John Erling Blad wrote:
>>> Can you explain why you use LocalStorage for this? It seems to me like
>>> this is the wrong solution and you should use cache manifests instead.
>>> LocalStorage is a quite limited area for _data_ storage and it will
>>> create problems if we start wasting that space for _code_ storage.
>>>
>>> John
>> _______________________________________________
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l


_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to