[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reliability of RPC services

From: Michal Suchanek
Subject: Re: Reliability of RPC services
Date: Thu, 27 Apr 2006 15:24:00 +0200

On 4/27/06, Pierre THIERRY <address@hidden> wrote:
> Scribit Michal Suchanek dies 25/04/2006 hora 11:54:
> > Because of encapsulation I should not be able to kill the plugin
> > separately from outside, and I do not need anyway. The browser either
> > knows it has killed the plugin or is killed as well. No problem.
> Why should it be a nothing or all case? First, I'm not so sure it would
> break encapsulation that much to be able to kill the plugin from
> outside. Or it breaks it, but it is desirable anyway.

How do you do that? If the plugin is started by the browser the
storage and cpu time is supplied by it. No other process needs to know
that the plugin was started. If you do not know it is running you
cannot killl it.

> On any current OS, if the plugin is a separate process, it will be
> killable (if the browser would recover is another story).
> And if you want to preserve encapsulation, why not let the user kill the
> plugin in the browser. If a plugin doesn't show anything or show

That's what I am talking about. The plugin is started and exclusively
used by the browser so there is no problem with providing an option to
kill it from the browser. Except it might make the browser user
interface more complex.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]