Show simple item record

dc.contributor.authorKrupczak, Bobbyen_US
dc.contributor.authorAmmar, Mostafa H. (Mostafa Hamed)
dc.contributor.authorCalvert, Kenneth L.
dc.date.accessioned2005-06-17T17:54:39Z
dc.date.available2005-06-17T17:54:39Z
dc.date.issued1995en_US
dc.identifier.urihttp://hdl.handle.net/1853/6680
dc.description.abstractProtocol software is often difficult, cumbersome, and expensive to implement and test in today's computing environments. To reduce this difficulty, several things are done: communications software is commonly subdivided into layers and organized into a protocol graph; it is developed within a protocol or networking subsystem; and it is often ported rather than developed from scratch. Inherent differences in the multitude of protocol subsystems offer a dizzying array of features, functionality, and drawbacks; their differences often reduce the portability and efficiency of protocol code. In this paper, we consider the 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.en_US
dc.format.extent195716 bytes
dc.format.mimetypeapplication/pdf
dc.language.isoen_US
dc.publisherGeorgia Institute of Technologyen_US
dc.relation.ispartofseriesCC Technical Report; GIT-CC-95-08en_US
dc.subjectProtocol software
dc.subjectCommunications software
dc.subjectLayers
dc.subjectProtocol graphs
dc.subjectPortability
dc.subjectPerformance
dc.subjectEfficiency
dc.subjectFeatures
dc.subjectProtocol subsystems
dc.titleMulti-Subsystem Protocol Architectures: Motivation and Experience with an Adapter-Based Approachen_US
dc.typeTechnical Reporteng_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record