| Plugin threads and stuff.. [message #22774] |
Fri, 11 April 2003 18:46  |
Eclipse User |
|
|
|
Originally posted by: kduffey.marketron.com
Hey all,
I know we can't controll all renegade developers and how they code things. I
am wondering what happens if a plugin creates a thread that uses part of the
ref to another plugin (or plugin class) to do its work, and if the plugin
class that this plugin depends on gets deactivated, unloaded, or reloaded,
what happens to the thread? My guess is it is up to the plugin lifecycle
event AND the code in the thread to properly check the object before each
use, but sometimes speed is of the essence so adding a lot of if() calls may
not be appropriate. How would such a scenario be handled?
|
|
|
| Re: Plugin threads and stuff.. [message #22818 is a reply to message #22774] |
Mon, 14 April 2003 09:54  |
| Eclipse User |
|
|
|
In this case, the plugin that has the thread must "require" (in the eclipse
sense) the plugin it uses.
According to the "deactivation" process, when a plugin gets deactivated all
the plugins
that relies on it can get deactivated too.
PaScaL
"Kevin" <kduffey@marketron.com> wrote in message
news:b77g6p$ot0$1@rogue.oti.com...
> Hey all,
>
> I know we can't controll all renegade developers and how they code things.
I
> am wondering what happens if a plugin creates a thread that uses part of
the
> ref to another plugin (or plugin class) to do its work, and if the plugin
> class that this plugin depends on gets deactivated, unloaded, or reloaded,
> what happens to the thread? My guess is it is up to the plugin lifecycle
> event AND the code in the thread to properly check the object before each
> use, but sometimes speed is of the essence so adding a lot of if() calls
may
> not be appropriate. How would such a scenario be handled?
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03002 seconds
Home