nspluginviewer priority on newer linux kernel

[James Richard Tyrer]

Thiago Macieira wrote:
> James Richard Tyrer wrote:
>> Yes, exactly.  The problem is that you need one process to send these
>> signals to the other process.  IIUC, listening at a socket doesn't
>> accomplish this.  That is to find out that the window doesn't have focus
>> and stop using the CPU.
> 
> That would require a change to the NSPlugin API. The plugins themselves 
> have to voluntarily stop what they are doing in a decent manner.

So, IIUC, Konqueror asks the plugin to stop and then waits for it to 
voluntary stop.  This would still be a large improvement.

> You cannot simply stop the process execution with SIGSTOP. That could lead 
> to problems like timers not working, internal clock going out of sync, 
> connections being dropped due to inactivity, etc.

OK, then you would need to reduce the priority to a very low one.

> Imagine you have a file-uploader plugin and you're uploading a large file 
> over a slow connection. You want to keep working while it uploads, so you 
> want the plugin to keep running in the background, while you switch to 
> other tabs and other programs.
> 
Yes, you want to do that, but what you don't want is user access to the 
window that currently has focus to be blocked.  That is the problem that 
needs to be solved.  When you click the mouse and nothing happens, that 
is an issue.

-- 
JRT