You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Danny Robinson <da...@gmail.com> on 2007/06/12 20:54:26 UTC
[Trinidad] Unique ID for merged javascript libs
We recently made some updates to the core javascript library in Trinidad.
These changes caused some headaches for users having to clear their browser
caches etc, so the updates were not seamless.
Should we use a similar unique id mechanism that was introduced for the
skins css files, so that changes cause a new filename to be generated, and
hence causing the browser to reload?
Is this feasible/possible?
Danny
--
Chordiant Software Inc.
www.chordiant.com
Re: [Trinidad] Unique ID for merged javascript libs
Posted by Adam Winer <aw...@gmail.com>.
OK, the version number on the Javascript is now 1_0_1.
Should help at least a bit.
-- Adam
On 6/12/07, Adam Winer <aw...@gmail.com> wrote:
> At a minimum, we should be bumping the version number on
> the Javascript. It's been at "m7"!?! for ages.
> I'll look at fixing that now. It doesn't help people moving from
> one snapshot to the next, but the theory is that 95% of people
> move from one released version to the next, and if you're on
> a snapshot, you have some extra headaches.
>
> -- Adam
>
>
> On 6/12/07, Danny Robinson <da...@gmail.com> wrote:
> > We recently made some updates to the core javascript library in Trinidad.
> > These changes caused some headaches for users having to clear their browser
> > caches etc, so the updates were not seamless.
> > Should we use a similar unique id mechanism that was introduced for the
> > skins css files, so that changes cause a new filename to be generated, and
> > hence causing the browser to reload?
> > Is this feasible/possible?
> >
> > Danny
> > --
> > Chordiant Software Inc.
> > www.chordiant.com
>
Re: [Trinidad] Unique ID for merged javascript libs
Posted by Adam Winer <aw...@gmail.com>.
At a minimum, we should be bumping the version number on
the Javascript. It's been at "m7"!?! for ages.
I'll look at fixing that now. It doesn't help people moving from
one snapshot to the next, but the theory is that 95% of people
move from one released version to the next, and if you're on
a snapshot, you have some extra headaches.
-- Adam
On 6/12/07, Danny Robinson <da...@gmail.com> wrote:
> We recently made some updates to the core javascript library in Trinidad.
> These changes caused some headaches for users having to clear their browser
> caches etc, so the updates were not seamless.
> Should we use a similar unique id mechanism that was introduced for the
> skins css files, so that changes cause a new filename to be generated, and
> hence causing the browser to reload?
> Is this feasible/possible?
>
> Danny
> --
> Chordiant Software Inc.
> www.chordiant.com