ftware, Inc.
303 438-9585
www.mhsoftware.com
> -Original Message-
> From: Ognjen Blagojevic [mailto:ognjen.d.blagoje...@gmail.com]
> Sent: Tuesday, April 12, 2011 1:06 PM
> To: users@tomcat.apache.org
> Subject: Re: OT: Versioning in Javascript Files
>
> Chris,
>
Chris,
href="some.css?v=${parameter}"
Some clients and proxies will refuse to cache resources with a query
string. In those cases, caching (obviously) won't work and there might
be a significant loss in performance of the web site.
Exactly. I tested on one usecase (no proxy, limited numbe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim,
On 4/12/2011 7:31 AM, Tim Funk wrote:
> The second is trickier. Relying on random query string is not fun since
> it may cause some browsers/proxies to be less prone to caching which can
> really affect performance. Especially if the the query st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ognjen,
On 4/12/2011 5:37 AM, Ognjen Blagojevic wrote:
> For all static resources (css, images, js) you might add artificial
> parameter that will trigger reload, like this:
>
> href="some.css?v=${parameter}"
Some clients and proxies will refuse t
On Tue, Apr 12, 2011 at 13:31, Tim Funk wrote:
[...]
>
> The second is trickier. Relying on random query string is not fun since it
> may cause some browsers/proxies to be less prone to caching which can really
> affect performance. Especially if the the query string is dynamic. An easier
> soluti
I've loathed this issue too. There are 2 major cases to deal with
- Libraries changing (like dojo, prototype, etc)
- Your external files changing
The first is "easy" to change .. in that you create a /scripts/ dir and
all 3rd party libraries go into their own directory with version number.
New
On 11.4.2011 23:47, George Sexton wrote:
I'm looking for ideas on how other people are doing versioning in Javascript
files. I'm hitting issues if I change my files in an incompatible way, or I
upgrade files.
For example, if I upgrade from DOJO 1.5 to DOJO 1.6, the user's browsers are
not always
On Mon, Apr 11, 2011 at 23:47, George Sexton wrote:
> I'm looking for ideas on how other people are doing versioning in Javascript
> files. I'm hitting issues if I change my files in an incompatible way, or I
> upgrade files.
>
> For example, if I upgrade from DOJO 1.5 to DOJO 1.6, the user's brow
I'm looking for ideas on how other people are doing versioning in Javascript
files. I'm hitting issues if I change my files in an incompatible way, or I
upgrade files.
For example, if I upgrade from DOJO 1.5 to DOJO 1.6, the user's browsers are
not always refreshing the DOJO files, and things don'
