A protocol conversion software toolkit
SIGCOMM '89 Symposium proceedings on Communications architectures & protocols
The X-Kernel: An Architecture for Implementing Network Protocols
IEEE Transactions on Software Engineering
A base for portable communications software
IBM Systems Journal
A dynamic network architecture
ACM Transactions on Computer Systems (TOCS)
Experimental evaluation of SUNOS IPC and TCP/IP protocol implementation
IEEE/ACM Transactions on Networking (TON)
The importance of non-data touching processing overheads in TCP/IP
SIGCOMM '93 Conference proceedings on Communications architectures, protocols and applications
A language-based approach to protocol implementation
IEEE/ACM Transactions on Networking (TON)
IEEE/ACM Transactions on Networking (TON)
Implementing network protocols at user level
IEEE/ACM Transactions on Networking (TON)
IEEE Transactions on Software Engineering
Rapid prototyping of mobile context-aware applications: the Cyberguide case study
MobiCom '96 Proceedings of the 2nd annual international conference on Mobile computing and networking
Increasing the portability and re-usability of protocol code
IEEE/ACM Transactions on Networking (TON)
Cyberguide: a mobile context-aware tour guide
Wireless Networks - Special issue: mobile computing and networking: selected papers from MobiCom '96
Hi-index | 0.00 |
Protocol software is often difficult and expensive to implement and test in today's computing environments. Several things are done to reduce this difficulty: communications software is subdivided into layers and organized into a protocol graph; communications software is developed within a protocol or networking subsystem; and it is often ported rather than developed from scratch. Today, a multitude of subsystems offer different features, functionality, and drawbacks; the differences among them often reduce portability and efficiency of protocol code. In this paper, we consider these differences in subsystems and their effect on the portability and performance of protocol implementations. We propose an approach for combining the better features of protocol subsystems by constructing protocol graphs composed of protocols residing in different subsystems. Our approach uses adapter modules spanning the inter-subsystem boundary. We relate our experiences designing, implementing, and measuring the performance of several such adapters using an AppleTalk protocol stack we have developed as a baseline.