PLAN: a packet language for active networks
ICFP '98 Proceedings of the third ACM SIGPLAN international conference on Functional programming
From system F to typed assembly language
ACM Transactions on Programming Languages and Systems (TOPLAS)
Smart packets: applying active networks to network management
ACM Transactions on Computer Systems (TOCS)
Proceedings of the ACM SIGPLAN 2001 conference on Programming language design and implementation
The Definition of Standard ML
IWAN '99 Proceedings of the First International Working Conference on Active Networks
RCANE: A Resource Controlled Framework for Active Network Services
IWAN '99 Proceedings of the First International Working Conference on Active Networks
Practical active packets
The SwitchWare active network architecture
IEEE Network: The Magazine of Global Internetworking
Open Packet Monitoring on FLAME: Safety, Performance, and Applications
IWAN '02 Proceedings of the IFIP-TC6 4th International Working Conference on Active Networks
Predictable, Lightweight Management Agents
IWAN '02 Proceedings of the IFIP-TC6 4th International Working Conference on Active Networks
Flexible network monitoring with FLAME
Computer Networks: The International Journal of Computer and Telecommunications Networking - Active networks
Hi-index | 0.00 |
PLAN( Packet Language for Active Networks) [3] is a highly flexible and usable active packet language, whereas SNAP (Safe and Nimble Active Packets) [12] offers significant resource usage safety and achieves much higher performance compared to PLAN, but at the cost of flexibility and usability. Ideally, we would like to combine the good properties of PLANw ith those of SNAP. We have achieved this end by developing a compiler that translates PLANi nto SNAP. The compiler allows us to achieve the flexibility and usability of PLAN, but with the safety and efficiency of SNAP. In this paper, we describe both languages, highlighting the features that require special compilation techniques. We then present the details of our compiler and experimental results to evaluate our compiler with respect to code size.