From 621c26567548e514fc793d35b208a3542b73f023 Mon Sep 17 00:00:00 2001 From: Jeffrey Armstrong Date: Wed, 14 Dec 2016 09:22:22 -0500 Subject: Updated readme --- readme.txt | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) (limited to 'readme.txt') diff --git a/readme.txt b/readme.txt index 6afae72..b039477 100644 --- a/readme.txt +++ b/readme.txt @@ -1,4 +1,4 @@ - uIP/FOSSIL Version 1.0 + uIP/FOSSIL Version 1.1 ====================== Welcome to the wonderful world of TCP/IP on MS-DOS! This package is @@ -28,20 +28,21 @@ compile on almost any ANSI C compiler. The code does not use any floating point mathematics. - This uIP port was engineered to compile using the OpenWatcom - compiler. The uIP project is contained in the topmost 'watcom' - directory. The entire project is stored in 'uip-rb.wpj', and a single - target, 'httpd.exe', has been defined for this project. + This uIP port was engineered to compile using either the OpenWatcom + compiler or the Turbo C 2.0 compiler. For OpenWatcom users, the uIP + project is contained in the topmost 'watcom' directory. The entire + project is stored in 'uip-rb.wpj', and a single target, 'httpd.exe', + has been defined for this project. Turbo C users can use the included + makefile to build the project. Prior to building the uIP project, the FosLib15 library must be built. The library provides a simplified C interface to the FOSSIL - driver. The library source code is located in 'slip/foslib15' - directory, and a watcom project file is located in the 'watcom' - subdirectory. - - A Makefile has been included that is compatible with Turbo C 2.0. - However, Turbo C seems to get confused during compile on certain files. - Use at your own risk... + driver. The library source code is available at: + + https://bitbucket.org/ArmstrongJ/foslib + + For both the OpenWatcom and Turbo C projects, FosLib15 should be + built using a medium memory model. The Web Server ============== @@ -57,6 +58,18 @@ The web server must be located in the same directory as the root web pages it will be serving. + + The web server will also check for equivalent, compressed files when + the client reports it accepts content with gzip encoding. Any HTML or + CSS files can be pre-compressed and stored on disk with the following + extensions: + + .HTM -> .HGZ + .CSS -> .CGZ + + Again, the files will be served as an alternative if available. The + web server will never compress files itself; that task is left to the + system administrator. Setting up SLIP on Linux ======================== @@ -76,4 +89,5 @@ jeff@rainbow-100.com http://jeff.rainbow-100.com/ January 31, 2009 + Updated December 14, 2016 -- cgit v1.2.3