Name
Abstract | ||
|---|---|---|
It appears that some degree of programmability is inevitable within the network, whether it be through active networks, active services, or programmable middleware. We argue that programming network elements with languages designed for use within a single machine is inappropriate, since the only defense for the shared resource of the network is through the use of sandboxes, which are prone to performance problems and are difficult to implement correctly. Instead, we believe that new languages should be designed for programmable networks, using type systems that ensure safe programs, and encourage correct programs. We have designed and provided the full semantics for such a language, SafetyNet. Building upon this, we have implemented a compiler, run time environment and a simulation environment for our language. In this paper we describe the major features of the language that protect the network: abstracted locations; located objects; volatile routing; thread and class loading; and enforced resource counting. We show how these features are used in a number of small case studies, and in implementing optimised communication libraries. We describe the implications of the language design for the implementation of the run time support environment. The ease with which these demonstrations have been built and debugged shows the potential for enforcing network programming models with well-typed languages. |
Year | DOI | Venue |
|---|---|---|
2001 | 10.1016/S1389-1286(01)00154-2 | Computer Networks |
Keywords | DocType | Volume |
Active networks,Strongly typed languages,Programming language design | Journal | 36 |
Issue | ISSN | Citations |
1 | Computer Networks | 8 |
PageRank | References | Authors |
0.80 | 18 | 4 |
Name | Order | Citations | PageRank |
|---|---|---|---|
| Ian Wakeman | 1 | 436 | 129.40 |
| Alan Jeffrey | 2 | 8 | 0.80 |
| Tim Owen | 3 | 31 | 3.28 |
| Damyan Pepper | 4 | 8 | 0.80 |