Hey Folks-
We're testing out the BrowserPlus notifier package which is really slick. One issue we're finding is that the BrowserPlus.initWhenAvailable( callback_ ) function, the CPU is spiking on our test machines. This is most noticeable in IE6, but also seems to use about 30% of the resources in FF.
Something you can look into?
Thanks,
---Marc
Hi Again Mark!
The full implementation of initWhenAvailable is here:
http://bp.yahooapis.com/2.1.11/browserplus.js(remove the -min to see unminified code)
here it is inline:
CODE
initWhenAvailable: function(initArgs, callback) {
setTimeout(function() {
try { navigator.plugins.refresh(false); } catch(e) { }
BrowserPlus.init(initArgs, function(r) {
if (r.success) {
callback(r);
} else {
BrowserPlus.initWhenAvailable(initArgs, callback);
}
});
}, 1000);
},
There are a couple ways to mitigate things in the short term:
1. reduce the poll period (rewrite initWhenAvailable)
2. ONLY call "initWhenAvailable" once the user has clicked on the upsell link
The more robust solution would be to dig into the javascript wrapper and figure out lighter weight ways to detect plugin presence. I'll get this on our todo list (which we should make public, btw).
What are the parameters of your test machine? We'll find a similar box to test on.
curious to hear more in attempts to mitigate or any feedback you may have on a proper solution :)lloyd
