pack:tag

First of all, love this library.

I've built something similar at flixster.com, but since it fails to
obfuscate prototype 1.6's new $super variables, I'm testing new libraries
in the market.

Here are my humble requests for pack:tag:

1) We would like to proxy all requests for javascript and css files through
a content delivery network (CDN). To do this, we'd need to prefix all
scripts with a url:
http://static.cdn.com/combined.js.1234.pack. It would be great if the
property "cache.servlet.combined.style.path" could support full urls,
instead of relative urls.

2) We have several webapp servers, and we load balance traffic between
them. So here's the potential problem:
- User's browser hits ourserver.com and gets loadbalanced to server A,
which generates/caches/references "combined.js.1234.pack" file.
- User's browser then requests script "combined.js.1234.pack", but this
request gets load balanced to server B.
- Server B fails to find "combined.js.1234.pack", since it has not yet
packed this script set yet.

Instead of using virtual paths, it would great if pack:tag generated a url
with all files as parameters:
eg, <scrpt src="/packer?file=1.js&file=2.js..."
and then execute the script consolidation/minification/obfuscation/caching
on the servlet (instead of during page generation). The problem with
virtual paths is that they are transient and only useful for cache
management, and probably shouldn't be used as public urls/keys...

Thanks for all of your great work, and hope you find my feedback useful.

Eugene Park
Flixster, Inc.