On Fri, May 9, 2008 at 4:56 PM, Chris Chabot <[EMAIL PROTECTED]> wrote:
> > On May 10, 2008, at 1:29 AM, Kevin Brown wrote: > > >> You know this is exactly what the java server does currently when you pass >> the libs parameter, right? The idea is that the container can aggregate >> what >> they expect the most commonly used features to be, and those are handled >> by >> /gadgets/js. Everything else is inlined. For example, on a production >> server: >> > > php shindig has the exact same ting, and was in fact what i was using with > most of my experimentation (with some slight alterations to test out having > separate script tags per feature vs one big blob) > > However that didn't give me any idea how to bypass the onLoad latency that > that would cause. > > if i would just do a libs=opensocial-0.7:settitle:etc, then the > onLoadHandlers() is called before the gadget.* calls become available, and > the whole thing errors out :) > > The way around this was to run the runOnLoadHandlers() on the actual page > load, with the added downside that this added some perceived latency .. how > do you deal with that? That's how we wound up doing it for the java implementation. The impact isn't significant enough to worry about it, and on firefox and safari it actually seems to be faster. > > -- Chris >
