#1992 NORM FRS: Activities need to be created inside containers.

[Zarro Boogs per Child]

#1992: Activities need to be created inside containers.
---------------------+------------------------------------------------------
  Reporter:  mstone  |       Owner:  mstone        
      Type:  defect  |      Status:  new           
  Priority:  normal  |   Milestone:  FRS           
 Component:  distro  |     Version:                
Resolution:          |    Keywords:  rainbow, sugar
  Verified:  0       |  
---------------------+------------------------------------------------------
Comment (by mstone):

 Indeed. I made a bug so questions like this won't get lost. (And so we
 remember to update the "Activity DBus API" page as you requested.

 The basic answer to your question in the thread is that calls to
 'create_activity()' are going to cause Rainbow to first make a new
 container and then start an executable specified by the named activity's
 activity.info file inside that container. In general, this executable will
 be the true activity executable and starting it will directly cause a new
 *instance* of the activity to be started in the newly created container.

 However, Rainbow doesn't much care what this executable does. Therefore,
 in special cases (e.g. Web and Etoys), it may be appropriate for the
 executable that Rainbow starts to make a DBus call against some actual
 factory process running in a different container to cause the new activity
 instance to be created by that factory process (or to become the factory
 process, if no such process exists).

 Is this a satisfactory answer to the question you posed?

-- 
Ticket URL: <http://dev.laptop.org/ticket/1992#comment:2>
One Laptop Per Child <http://laptop.org/>