I don't understand why the Ajaxian article and the API docs prefer the google.load() route. Since the paths are published in the Google CDN, I would personally prefer those but I may be missing something important. By using the google.load, it seems like you could get the smart versioning or ensure that any future path changes will be silent to your app; on the other hand, by using the published path I know what URL will get cached and I 'know' what I'm getting. Is there something else about google.load() that I should be thinking about? - jeremiah> Date: Tue, 27 May 2008 09:55:15 -0700> Subject: [jQuery] Re: jQuery Google CDN> From: [EMAIL PROTECTED]> To: jquery-en@googlegroups.com> > > Nice one!> > > www.subprint.com> > On May 27, 10:57 am, "Jake McGraw" <[EMAIL PROTECTED]> wrote:> > Just tried it out, works very nice, glad to see Google hopping on the> > YUI band wagon for hosting library files.> >> > - jake> >> > On Tue, May 27, 2008 at 11:49 AM, Glen Lipka <[EMAIL PROTECTED]> wrote:> > > Not sure if everyone saw this. Looks great to me. I think I will switch> > > asap.> > >http://code.google.com/apis/ajaxlibs/> >> > > Originally read here:> > >http://ajaxian.com/archives/announcing-ajax-libraries-api-speed-up-yo...> >> > > Glen _________________________________________________________________ E-mail for the greater good. Join the i’m Initiative from Microsoft. http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_ GreaterGood
