Connected: An Internet Encyclopedia
RFC 1144 - A Sample Implementation

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1144
Prev: References
Next: A.1 Definitions and State Data

### A Sample Implementation

The following is a sample implementation of the protocol described in this document.

Since many people who might have the deal with this code are familiar with the Berkeley Unix kernel and its coding style (affectionately known as kernel normal form), this code was done in that style. It uses the Berkeley `subroutines' (actually, macros and/or inline assembler expansions) for converting to/from network byte order and copying/comparing strings of bytes. These routines are briefly described in sec. A.5 for anyone not familiar with them.

This code has been run on all the machines listed in the table on page 24. Thus, the author hopes there are no byte order or alignment problems (although there are embedded assumptions about alignment that are valid for Berkeley Unix but may not be true for other IP implementations --- see the comments mentioning alignment in sl_compress_tcp and sl_decompress_tcp).

There was some attempt to make this code efficient. Unfortunately, that may have made portions of it incomprehensible. The author apologizes for any frustration this engenders. (In honesty, my C style is known to be obscure and claims of `efficiency' are simply a convenient excuse.)

This sample code and a complete Berkeley Unix implementation is available in machine readable form via anonymous ftp from Internet host ftp.ee.lbl.gov (128.3.254.68), file cslip.tar.Z. This is a compressed Unix tar file. It must be ftped in binary mode.

All of the code in this appendix is covered by the following copyright:

       /*
        * Copyright (c) 1989 Regents of the University of California.
        * All rights reserved.
        *
        * Redistribution and use in source and binary forms are
        * permitted provided that the above copyright notice and this
        * paragraph are duplicated in all such forms and that any
        * documentation, advertising materials, and other materials
        * related to such distribution and use acknowledge that the
        * software was developed by the University of California,
        * Berkeley.  The name of the University may not be used to
        * endorse or promote products derived from this software
        * without specific prior written permission.
        * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS
        * OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE
        * IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A
        * PARTICULAR PURPOSE.
        */

A.1 Definitions and State Data
A.2 Compression
A.3 Decompression
A.4 Initialization
A.5 Berkeley Unix dependencies

Next: A.1 Definitions and State Data

Connected: An Internet Encyclopedia
RFC 1144 - A Sample Implementation