--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"\r
+ "http://www.w3.org/TR/1999/REC-html401-19991224/frameset.dtd">\r
+<HTML>\r
+<HEAD>\r
+ <!-- Created by NaviPress/1.2 -->\r
+ <TITLE>Jigsaw User's Guide</TITLE>\r
+<!-- Changed by: Anselm Baird-Smith, 4-Feb-1997 -->\r
+</HEAD>\r
+<FRAMESET COLS="30%,70%" >\r
+ <FRAME SRC="fr-toc.html" SCROLLING=yes>\r
+ <FRAME SRC="fr-Overview.html" NAME="jigsaw-help">\r
+<NOFRAMES>\r
+\r
+<H1>\r
+ <A HREF="http://www.w3.org/pub/WWW/" TARGET="_top_"><IMG SRC="/icons/WWW/w3c_home" ALT="w3c" WIDTH="72"\r
+ HEIGHT="48" BORDER="0"></A>\r
+ <A HREF="../" TARGET="_top_"><IMG SRC="/icons/jigsaw.gif" WIDTH="212"\r
+ HEIGHT="49" ALT="Jigsaw" BORDER="0"></A>\r
+</H1>\r
+<H1>\r
+ Jigsaw user's guide\r
+</H1>\r
+<H2>\r
+ Design\r
+</H2>\r
+<P>\r
+The <STRONG>Jigsaw</STRONG> server is entirely written in Java. Because of\r
+this, it offers the following features:\r
+<DL>\r
+ <DT>\r
+ Portable\r
+ <DD>\r
+ <STRONG>Jigsaw</STRONG> will run on all platforms that support Java, with\r
+ <EM>no</EM> changes ! This is for real, it has been tested at least on Windows\r
+ 95 and Windows NT.\r
+ <DT>\r
+ Extensible\r
+ <DD>\r
+ <STRONG>Jigsaw</STRONG> is made of a core and a set of extension modules.\r
+ You can add your own modules, <EM>dynamically</EM>, to the server. Moreover,\r
+ because the Java runtime comes with both threads and garbage collection,\r
+ your job as an extension writter is largely simplified.\r
+ <DT>\r
+ Object Oriented\r
+ <DD>\r
+ The full code of the server is object-oriented, but the interesting thing\r
+ is that resources <EM>are objects</EM>. By opposition to most of the existing\r
+ servers, that consider a resource as being either a <B>cgi script</B> or\r
+ a <B>file</B>, <STRONG>Jigsaw</STRONG> allows <EM>any</EM> object to become\r
+ accessible through HTTP.\r
+</DL>\r
+<H2>\r
+ Table of content\r
+</H2>\r
+<P>\r
+<B>Jigsaw</B> user's guide is made of the following material:\r
+<DL>\r
+ <DT>\r
+ <B><A HREF="Introduction/Overview.html">Presentation</A></B>\r
+ <DD>\r
+ A quick overview at the <B>Jigsaw</B> architecture. This is a good starting\r
+ point if you want to either use or extend <B>Jigsaw</B>. It will explains\r
+ you the basic design.\r
+ <DT>\r
+ <A HREF="Administration/Overview.html"><B>Jigsaw</B> administration guide</A>\r
+ <DD>\r
+ The thing you want to read if you are planning to use <B>Jigsaw</B> as your\r
+ HTTP server. This will explain you how to configure <B>Jigsaw</B>.\r
+ <DT>\r
+ <A HREF="Tutorials/Overview.html"><B>Jigsaw</B> tutorials</A>\r
+ <DD>\r
+ Three tutorials, that explain you how to run and configure <B>Jigsaw</B>,\r
+ how to extend by by writing new resources, and how to extend it by writing\r
+ new filters.\r
+ <DT>\r
+ <A HREF="Reference/Overview.html"><B>Jigsaw</B> reference manual</A>\r
+ <DD>\r
+ The reference documentation for all <B>Jigsaw</B> objects. This includes\r
+ reference documentation for the set of Java properties used by the server,\r
+ the set of pre-defined resources and the set of pre-defined filters.\r
+ <DT>\r
+ <A HREF="api/packages.html"><B>Jigsaw</B> application programming interface</A>\r
+ <DD>\r
+ The thing you want to read if you plan to extend <B>Jigsaw</B> with new\r
+ functionalities. This includes writing new resource objects (a kind of CGI\r
+ in the server), changing the default logger, etc.\r
+</DL>\r
+<P>\r
+They should be read in this order: it is recommeneded to be able to configure\r
+<B>Jigsaw</B> before trying to extend it !\r
+<P>\r
+ <HR>\r
+<P>\r
+<A HREF="mailto:jigsaw@w3.org">Jigsaw Team</A><BR>\r
+$Id: Overview.html,v 1.1 2010/06/15 12:28:14 smhuang Exp $\r
+<P>\r
+</NOFRAMES></FRAMESET></HTML>\r
projects / Benchmarks_CSolver.git / blobdiff