Compression and delivery of web server content

Abstract

A server-side mechanism together with an optional client-side decompression process enhance server content delivery. The server-side mechanism preferably comprises a pair of processes: a daemon process and a servlet process. The daemon process recursively compresses directories of content (HTML, graphics files, and the like) while instances of the servlet process, in parallel, serve content. When a target directory is completely compressed, the files which previously existed in an uncompressed state are either archived or deleted. The servlet process interprets the compressed objects, resolving the connection between the client and server, and serves out the requested content. If the request originates from a client that is not enabled to decompress files, the servlet decompresses the requested files on-the-fly. When supported on a given client machine, the client process decompresses the streaming content for use on the client system.

Dependencies are inferred from the claim text.