Walnut/Persistent Secure Distributed Computing
From Erights
(→Persistent Secure Distributed Computing: some wikifying) |
|||
Line 3: | Line 3: | ||
==Persistent Secure Distributed Computing== | ==Persistent Secure Distributed Computing== | ||
- | There is a problem with the programs we explored in the last chapter. The MarketPlace server, the RaceTrack server, and eChat are not persistent: once you shut them down they are gone forever. You can start up a new server with the same code, but it will not return to life with the same | + | There is a problem with the programs we explored in the last chapter. The MarketPlace server, the RaceTrack server, and eChat are not persistent: once you shut them down they are gone forever. You can start up a new server with the same code, but it will not return to life with the same [[wikipedia:Uniform Resource Identifier|URI]] it had before. As a consequence, if you restart a server, you must redistribute the [[capability]] to access that server to all the users. This is a logistical nightmare. When we restart one of these servers, it must be able to restart with the same [[vatID]] and object IDs it had before. |
- | If | + | If '''''E''''' simply allowed objects to remember their own URIs, there would be extensive opportunities for object forgery in the mobile code systems described in the next chapter. To prevent such forgeries, '''''E''''' uses ''[[swiss base]]s'' for persistence. |
===Swiss Bases=== | ===Swiss Bases=== |
Revision as of 16:48, 1 January 2007
Persistent Secure Distributed Computing
There is a problem with the programs we explored in the last chapter. The MarketPlace server, the RaceTrack server, and eChat are not persistent: once you shut them down they are gone forever. You can start up a new server with the same code, but it will not return to life with the same URI it had before. As a consequence, if you restart a server, you must redistribute the capability to access that server to all the users. This is a logistical nightmare. When we restart one of these servers, it must be able to restart with the same vatID and object IDs it had before.
If E simply allowed objects to remember their own URIs, there would be extensive opportunities for object forgery in the mobile code systems described in the next chapter. To prevent such forgeries, E uses swiss bases for persistence.
Swiss Bases
Example: Persistent eChat
Next Section: Secure Mobile Code