mojo: terminate apps if the shell goes away

mojo/public/interfaces/service_provider/service_provider.mojom

 // Copyright 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Quick definitions:
 // The Shell is the finder and launcher of Applications.
 // Applications vend Services through the ServiceProvider interface.
 // Services implement Interfaces.
 // An Application uses it's Shell interface to connect to other Applications.
 module mojo {
 
 [Client=ServiceProvider]
 interface ServiceProvider {
   // Loads url. mojo:{service} will result in the the value of the
   // --origin flag to the shell being used.
   ConnectToService(string interface_name, handle<message_pipe> client_handle);
 };
 
 // TODO(davemore): Break Application & Shell into their own files.
 [Client=Application]
 interface Shell {
   // Loads url. mojo:{service} will result in the user of the value of the
   // --origin flag to the shell being used.
   ConnectToApplication(string application_url, ServiceProvider& provider);
 };
 
 [Client=Shell]
 interface Application {
   AcceptConnection(string requestor_url, ServiceProvider provider);
+  Terminate();

[darin (slow to review), 2014/07/28 16:49:58]

I'm not sure this is the API we want for application lifetime. I'm not sure we
want any explicit "you should shutdown" event. We may be better served only
providing "suspend/resume" events. If suspended, you might be killed. However, I
guess the issue is that we need some kind of explicit "now you are killed" event
to handle the case of single process mode or multiple apps loaded into the same
process? Hmm...

[tim (not reviewing), 2014/07/28 16:55:17]

If the primordial app exits and we want to quit the shell, we'll want to kill
other apps...

 };
 
 }