The way I would like it to be is that the current functionality of Tap is the
default and the per folder would be configurable, like (pseudocode)
@Contribute
public static void contributeFolderChecksum(conf) {
conf.add("classpath://org.dh.wymeditor.js");
}
and only that path and subfoldrs would get the per folder treatment. As said, I
don't know how hard this would be implement, so I'm not sure if it is feasible.
If it would be feasible, then it comes down to the trade off between doing the
redirects vs. downloading all the content in the given directory if something
changes. For a library that updates seldom I think the folder approach is
better, but for library that is massive and only small portions change
frequently the redirects would be better.
As a developer I would like to be the one who makes the call, so perhaps I'll
learn the source code first :D
Ville
-----Alkuperäinen viesti-----
Lähettäjä: Thiago H de Paula Figueiredo [mailto:[email protected]]
Lähetetty: 12. syyskuuta 2013 18:02
Vastaanottaja: Tapestry development
Aihe: Re: [5.4] Problems with the asset checksums and relative paths based on
them
On Thu, 12 Sep 2013 09:43:40 -0300, Barry Books <[email protected]> wrote:
> If you have file a b and c. The page includes a which then includes b
> and c but in your case with a's checksum.
In my case, Tapestry can't know that file a included b and c, because a, which
is JavaScript, dynamically included them in the page. It just knows b and c
were requested with wrong checksums.
> If Tapestry just returned b and c with a's checksum everything would
> work fine. The only problem would be if you change b or c without
> changing a. I agree this could be a problem but if you are using a
> library with releases I would say the odds of this happening are low
> and is easily fixed by just changing a.
Ville's solution does fix my problem, but it creates another: if you have a, b,
c in the same folder and you change one of them, a, b, c will have their
checksums changed. I don't think the odds of this happening are low.
Just changing another file which didn't need to be changed just to keep
Tapestry happy, I'm sorry, I think it's quite bad.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
