msocket: multiple stack support for the berkeley socket API

Authors:
Renzo Davoli;Michael Goldweber
Affiliations:
University of Bologna, Italy;Xavier University
Venue:
Proceedings of the 27th Annual ACM Symposium on Applied Computing
Year:
2012

Citing 3
Cited 1

An Architectural Overview of QNX

Proceedings of the Workshop on Micro-kernels and Other Kernel Architectures
Zero Copy Sockets Direct Protocol over InfiniBand — Preliminary Implementation and Performance Analysis

HOTI '05 Proceedings of the 13th Symposium on High Performance Interconnects
View-OS: A New Unifying Approach Against the Global View Assumption

ICCS '08 Proceedings of the 8th international conference on Computational Science, Part I

P/S sockets: supporting publish/subscribe communication through the standard socket API

Proceedings of the 8th Workshop on Middleware for Next Generation Internet Computing

Quantified Score

Hi-index	0.00

Visualization

Abstract

The de-facto standard for network programming, the Berkeley socket API, supports several protocol families. Unfortunately, it has a significant limitation in only allowing a single implementation for each supported protocol family. Hence, using Berkeley sockets, it is impossible to access multiple distinct networking stacks for the same protocol, e.g. multiple TCP/IP stacks. This paper defines, msocket, an extension to the Berkeley socket API which overcomes this limitation. msocket has been implemented as a feature of the View-OS project. Finally, we illustrate the utility and effectiveness of our extended API by providing some examples of its use.