<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 15/08/2020 08:56, Trygve Reenskaug
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:2c5f0fa5-9f56-5d37-bdf8-964a62f698f2@ifi.uio.no">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Just an idea while a car is waiting to take me on a vacation.<br>
<br>
Imagine:<br>
<ol>
<li>You have a computer with many independently running images.</li>
<li>A super fast facility pass messages between the images,</li>
<li>Selected services in the release image are move out and
deployed as server objects in another image.</li>
<li>Every image appears as a server offering RESTful interfaces
to other images.</li>
<li>Selected packages in any repository can be downloaded,
compiled, instantiated, and deployed in an image as server
objects.</li>
<li>The different images can even run in different computers and
use different VMs.<br>
</li>
<li>There are now two dimensions to the reuse of functionality:
a) download and compile a package. b In some image, install a
package and deploy it as a server object.</li>
<li>And presto: The original image is now small and manageable
while the whole system can grow without increasing the
complexity of the release image.</li>
</ol>
In haste. This is just an idea. It's full of holes and need a lot
of work done to it before it can be usable.. It's a disruptive
idea, so please give it some consideration This is before you
shoot it down<br>
--Trygve<br>
<br>
</blockquote>
<p>Sort of like using Images as Actors?<br>
</p>
</body>
</html>