head	1.6;
access;
symbols;
locks; strict;
comment	@# @;


1.6
date	2002.08.21.19.48.58;	author grendel;	state Exp;
branches;
next	1.5;

1.5
date	2002.08.21.10.25.43;	author jnt;	state Exp;
branches;
next	1.4;

1.4
date	2002.08.21.09.35.34;	author grendel;	state Exp;
branches;
next	1.3;

1.3
date	2002.08.21.09.22.49;	author grendel;	state Exp;
branches;
next	1.2;

1.2
date	2002.08.21.01.15.57;	author grendel;	state Exp;
branches;
next	1.1;

1.1
date	2002.08.21.01.13.08;	author grendel;	state Exp;
branches;
next	;


desc
@@


1.6
log
@wrapped the longish line
@
text
@What is C4?
===========

C4 is a WebServer written in Pike (http://pike.ida.liu.se/)


Why another WebServer?
======================
First of all - and we really feel we must stress ourselves on this point  - C4
isn't just another webserver.  C4 is an extremely fast, flexible and extensible
networking engine.  The big idea is that the core of C4 is a marshall, which
handles communication between various transports (for example, the HTTP protocol transport), 
various components (for example, the web server component).
What this all boils down to, is that C4 is not a webserver, but is also a webserver.


$Id: README,v 1.5 2002/08/21 10:25:43 jnt Exp $
@


1.5
log
@Sorry. I've been reading lots of Douglas Adams
@
text
@d12 2
a13 1
handles communication between various transports (for example, the HTTP protocol transport), various components (for example, the web server component).
d17 1
a17 1
$Id: README,v 1.4 2002/08/21 09:35:34 grendel Exp $
@


1.4
log
@more mailing list testing
@
text
@d9 5
d16 1
a16 1
$Id: README,v 1.3 2002/08/21 09:22:49 grendel Exp $@


1.3
log
@testing the mailing list
@
text
@d6 6
a11 1
$Id: README,v 1.2 2002/08/21 01:15:57 grendel Exp $@


1.2
log
@added some more blurb
@
text
@d6 1
a6 3
blah blah

$Id: README,v 1.1 2002/08/21 01:13:08 grendel Exp $@


1.1
log
@added readme
@
text
@d4 1
d6 3
a8 1
$Id$@

