[Cosmo-dev] Cacheing bugs on cosmo js

[Bobby Rullo]

On Feb 7, 2007, at 3:11 PM, Matthew Eernisse wrote:

> After digging a bit, it appears that the query string option is not  
> that attractive considering our support for Safari. From this article:
>
> http://www.thinkvitamin.com/features/webapps/serving-javascript-fast
>
> "According the letter of the HTTP caching specification, user  
> agents should never cache URLs with query strings. While Internet  
> Explorer and Firefox ignore this, Opera and Safari don’t - to make  
> sure all user agents can cache your resources, we need to keep  
> query strings out of their URLs."
>
> Using a query string would mean that our good friend Safari would  
> *never* cache the file, which is probably not what we want either.
>
> Here's an idea -- has anybody suggested doing some URL rewriting  
> magic to map a versioned path to the real 'js' directory in the web  
> app? Could the build process take care of keeping that mapping up  
> to date?
>

That's actually a frickin' brilliant idea! We could use URLRewrite I  
think, right?

> Something like:
>
> /js-SNAPSHOT-0.6/ => /js/
>
> Just trying to consider all the possibilities.
>
>
> M.
>
>
> Travis Vachon wrote:
>> The big reason is that we'd need to change this in SVN between  
>> releases. Because the "lib" directory is generated by the build  
>> process, we can add this information there.
>> -Travis
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev