greenlaw110/greenscript — pull request #32 by tazmaniax (2012-01-27 21:02:14+00:00)
Title: Cache key now MD5 hash of the resource names being combined

Hi Green,

I'll have to admit that I'm not 100% understanding of all the code so I've focused on the UUID.randomUUID(). Assuming that an MD5 hash of the concatenated resource names provides a reliable hash without any collisions in the majority of cases would this provide the necessary predictable naming required by a cluster without the need of engaging a separate shared cluster wide cached index that you suggested? Or have I completely missed the boat?

I'm in the process of testing but I thought I'd get a heads up to see if it was a likely solution.

It looks like Minimizer.process(List resourceNames) is where the magic happens but I couldn't see how this was called from GreenScriptPlugin. I'm guessing on startup all the managed files are compressed and combined.

cheers,
Chris