> but why shouldn't libraries actually deliver the whole packages with them and > set a common id on it - and it's wicket to decide which location came first? > it's no problem of data-redundancy in the jars, but contributing more than > once > to the browser.
If you would allow for multiple links to an id, Wicket could try until it finds one for every request that comes in. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
