Another alternative would be a "ping" type call to say "I'm
unresponsive, and I mean it." Like a watchdog timer. The plug-in
could still effectively be hung, but at least it has to have things
together enough to call the watchdog.
-scott
On Fri, Sep 11, 2009 at 3:37 PM, John Abd-El-Malek <j...@chromium.org> wrote:
> For reference, something similar is done for popups:
> void NPN_PushPopupsEnabledState(NPP instance, NPBool enabled);
> void NPN_PopPopupsEnabledState(NPP instance);
> Perhaps we can do the same thing here:
> void NPN_PushPluginHangDetectorState(NPP instance, NPBool enabled);
> void NPN_Pop PluginHangDetectorState(NPP instance);
> On Fri, Sep 11, 2009 at 2:46 PM, John Tamplin <j...@google.com> wrote:
>>
>> On Fri, Sep 11, 2009 at 5:24 PM, Darin Fisher <da...@chromium.org> wrote:
>>>
>>> I think that is a reasonable feature request. It would be nice however
>>> if there were some way to know when to restore the old behavior.
>>> Unfortunately, Chrome won't know when you are done.
>>
>> I was thinking something like this for my case (substitute appropriate
>> method names):
>> NPN_SetPluginWarning(false);
>> processSocketMessages();
>> NPN_SetPluginWarning(true);
>> and trying to call NPN_SetPluginWarning where you didn't request that
>> permission in the manifest would fail.
>>
>> --
>> John A. Tamplin
>> Software Engineer (GWT), Google
>>
>>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
