next up previous
Next: Security Up: Loading application-specific code Previous: Loading application-specific code


Code and available operations

To enable clients to load code into the network, there is an operation in the Sandman's secondary interface which takes as arguments a policy and a start time tstart at which time the application wants the policy to be run. This is illustrated in Figure [*]. At start of day, the implementation of the Sandman has two public interfaces: one for the primary operations and one for the secondary operations. The tertiary interface need not be publicly accessible. Note that restrictions may be placed on the number of DLAs allowed in the MCA as well as on the amount of CPU time each DLA gets. An interface to the DLA enables remote applications (e.g. the parent) to communicate with it. This allows DLAs to make arbitrary extensions to the core functionality of the Sandman. The operations that are made available to the DLA range from the usual operations that are available to normal applications (i.e. the primary and secondary operations) to the low-level tertiary operations.

Figure: Netlet in virtual network
\includegraphics[width=2.35in]{vnets.eps}
Figure: Partitioning switches
\includegraphics[width=2.35in]{loadable.eps}

Figure: Application code injected in the network
\includegraphics[width=3in]{loadable.eps}


next up previous
Next: Security Up: Loading application-specific code Previous: Loading application-specific code
Herbert Bos
2001-12-11