<p>Then there's the lovely version issue, when each lib depends on a different jquery... oops; ) that one shouldn't happen too much, but Its worth considering... might be easy just to say "you're on your own"</p>
<p>Lincoln Baxter III<br>
<a href="http://ocpsoft.com">http://ocpsoft.com</a><br>
<a href="http://scrumshark.com">http://scrumshark.com</a><br>
Keep it simple.</p>
<p><blockquote type="cite">On Dec 23, 2009 3:09 PM, "Dan Allen" <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>> wrote:<br><br><div class="gmail_quote"><p><font color="#500050">On Mon, Dec 21, 2009 at 4:12 AM, Werner Punz <<a href="mailto:werner.punz@gmail.com">werner.punz@gmail.com</a>> wrote:
>
> a) The import part, ...</font></p><div>I just thought it would be interesting if two components that requested something like jQuery (even in different libraries) would recognize that they are both asking for the same thing and just put one of them in the head. I think that happens automatically if they happen to use the same resource name. But if they are in different JAR files, then the resource name won't be the same and a duplicate will be sent. So some sort of global identifier much be nice for the most popular libraries.<br>
<font color="#888888">
<br>-Dan<br></font></div></div><p><font color="#500050">
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #2...</font></p></blockquote></p>