Re: Shutting down VatTP

On Oct 15, 2010, at 11:50, Thomas Leonard wrote:

> It's quite useful to be able to restart a vat without having to  
> restart
> the whole JVM. This requires shutting down the listing sockets (among
> other things), so that the new vat can start listening on the existing
> socket.
>
> What's the best way to do this? I got it working in a hacky way like
> this:
>
> http://gitorious.org/~tal-itinnov/repo-roscidus/it-innovation/commit/8b94a34e9e45df1ea3cdf933bfe3c96dedb2c317

This is wrong: once onTheAir, the introducer should be safe to expose  
to untrusted clients that you're not bit-confining (that is, be  
defensively consistent): giving it a shutdown operation breaks this.

> - How should this be exposed to E code?
[...]
> - Should vat.orderlyShutdown do this automatically?

It seems to me that orderlyShutdown of a vat should shut down its  
Pluribus stack. I see no reason to do otherwise, and I am surprised it  
doesn't do so already.

> - What else needs to be done?

I'm not an expert on this part of the implementation of the old CapTP  
implementation.

-- 
Kevin Reid                                  <http://switchb.org/kpreid/>