> Is there a way to dress it up a bit, so that based on sessions, if the
> images are already cached it will skip them. or would that be unnecessary?
In theory, it would be unnecessary; in practice, it is a good idea to
minimize references to remote assets so that browsers' "heuristic"
cachebusting measures are less likely to kick in. So you could just
check for a session cookie before Asset.images(), n'eh?
That said, if you're expecting to manage caching solely at the client
side, you're doing it wrong. What you want is to serve these images
with far-future Expires: headers -- if the images change, then your
markup/CSS should fetch them at a new path (a new query string works
most of the time, but a new path is even better to deal with old
proxies that think query string == no-cache). My advice is to have a
cacheme.example.com subdomain from which *everything* expires in the
distant future; no dynamic URIs ever come from that domain.
Steve Souders' blog is the primary resource for this stuff.
-- Sandy