Person:
Ammar, Mostafa H.

Permanent Link
https://hdl.handle.net/1853/71056
Associated Organization(s)
Organizational Unit
ORCID
ArchiveSpace Name Record

Filters

1995 - 1996 2
2
2
2
2
Reset filters

Settings
Author: Calvert, Kenneth L. × Author: Krupczak, Bobby × search.filters.applied.f.isSeriesOfPublicationTitle: College of Computing Technical Report Series × Type: Text ×

Publication Search Results

Now showing 1 - 2 of 2
Thumbnail Image
Item

Protocol Portability through Module Encapsulation

1996 , Calvert, Kenneth L. , Ammar, Mostafa H. , Krupczak, Bobby

Because protocol software is difficult and expensive to implement and test, it is often ported between systems, instead of being rewritten from scratch. Unfortunately, porting protocol software can be nearly as difficult as from-scratch development, due to inherent differences in subsystem design and services provided. Thus, protocol subsystems can have a profound effect on the portability of a protocol implementation. In this paper, we propose an approach permitting the incorporation of new protocols into a subsystem other than their "native" one, without the drawbacks or expense of porting and original development. Our approach is based on protocol module encapsulation, which allows unmodified protocol code developed for one protocol subsystem to be used within another. We relate our experiences designing, implementing, and measuring the performance of our protocol encapsulation modules, using an AppleTalk protocol stack as a baseline.

View
Thumbnail Image
Item

Multi-Subsystem Protocol Architectures: Motivation and Experience with an Adapter-Based Approach

1995 , Ammar, Mostafa H. , Calvert, Kenneth L. , Krupczak, Bobby

Protocol 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.

View