Re: Reliability of RPC services

[Pierre THIERRY]

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.

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
something obviously wrong, the user won't have much difficulty
understanding where the problem lies. If it has an option 'kill that
plugin', there are chances it will. If a barking watchdog suggests it in
addition, we can be sure it will.

> But if OpenOffice uses a posix layer it just tries to open the file.
> It should still be possible to cancel the operation in OpenOffice but
> it will probably stay in progress inside the posix layer indefinitely.
> Introducing any proxies or layers for whatever reason introduces such
> problems.

If we design the POSIX layer well, this one could receive the notice
that operation will not complete (from the driver framework or not), and
forward it to OpenOffice as a POSIX error in the read operation.

Quickly,
Nowhere man
-- 
address@hidden
OpenPGP 0xD9D50D8A

signature.asc
Description: Digital signature