--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"\r
+ "http://www.w3.org/TR/REC-html40/loose.dtd">\r
+<html>\r
+<head>\r
+ <title>Jigsaw Frequently asked questions</title>\r
+ <link rel="stylesheet" type="text/css" href="style/doc.css">\r
+ <meta http-equiv="Content-Type" content="text/html">\r
+</head>\r
+\r
+<body bgcolor="#FFFFFF">\r
+\r
+<div class="icons-w3c">\r
+<a href="../../"><img src="/Icons/w3c_home" border="0" alt="W3C logo"\r
+height="48" width="72"></a></div>\r
+\r
+<div class="icons-jigsaw">\r
+<a href="../"><img src="/Icons/jigsaw" border="0" alt="Jigsaw" height="49"\r
+width="212"></a></div>\r
+\r
+<div class="title">\r
+<h1 class="title">Jigsaw <br>\r
+<span class="subtitle">Frequently Asked Questions</span></h1>\r
+<hr noshade="noshade" width="70%" align="left">\r
+<a href="../Overview.html">Jigsaw Home</a> / <a\r
+href="Overview.html">Documentation Overview</a></div>\r
+\r
+<div class="body">\r
+<h1>What is <b>Jigsaw</b> ?</h1>\r
+<ul>\r
+ <li><a href="#purpose">What's the purpose of <b>Jigsaw</b>, why yet another\r
+ server ?</a></li>\r
+ <li><a href="#download">Where can I get <b>Jigsaw</b> ?</a></li>\r
+ <li><a href="#java">Why is <b>Jigsaw</b> written in Java ?</a></li>\r
+ <li><a href="#slow"><b>Jigsaw</b> is written in Java, it must be really\r
+ slow...</a></li>\r
+</ul>\r
+\r
+<h1>Using <b>Jigsaw</b></h1>\r
+<ul>\r
+ <li><a href="#Method-GET">The admin server reply "Method GET not\r
+ implemented.", how can I use it?</a></li>\r
+ <li><a href="#jigsaw-indexing">What's this <i>indexing</i> thing all about\r
+ ?</a></li>\r
+ <li><a href="User/authentication.html">How do I setup authentication\r
+ ?</a></li>\r
+ <li><a href="#pass-directory">How do I tie a resource to a directory not\r
+ under my server root?</a>[Sirilyan sirilyan@io.com]</li>\r
+ <li><a href="#CGI-scripts">How do I setup a CGI script ?</a></li>\r
+ <li><a href="#php3">How can I use php3 in <b>Jigsaw</b>?</a></li>\r
+ <li><a href="User/jsp.html">How can I use jsp in <b>Jigsaw</b>?</a></li>\r
+ <li><a href="User/proxy.html">How do I setup <b>Jigsaw</b> as a proxy\r
+ ?</a></li>\r
+ <li><a href="User/virtual-hosting.html">How do I setup virtual hosting in\r
+ <b>Jigsaw </b>?</a></li>\r
+ <li><a href="#index">How do I set the default document?</a></li>\r
+ <li><a href="User/mimetype.html">How to add a new Mime Type in\r
+ Jigsaw?</a></li>\r
+ <li><a href="#ssl">Does Jigsaw support SSL?</a></li>\r
+ <li><a href="#login">What is the default Login Name and Password for\r
+ JigAdmin?</a></li>\r
+</ul>\r
+\r
+<h1>Technical stuff</h1>\r
+<ul>\r
+ <li><a href="#extend">How can I extend <b>Jigsaw</b> ?</a></li>\r
+ <li><a href="Programmer/compile.html">How do I compile Jigsaw?</a></li>\r
+ <li><a href="#persist">Why does <b>Jigsaw</b> implements its own persistence\r
+ mechanism ?</a></li>\r
+ <li><a href="#client-hotjava">How can I use HotJava on top of your HTTP\r
+ client API ?</a></li>\r
+ <li><a href="#http-port">Running <b>Jigsaw</b> on port 80 under\r
+ UNIX</a></li>\r
+ <li><a href="#chroot">Chrooting <b>Jigsaw</b> under UNIX</a></li>\r
+ <li><a href="#Running">Running <b>Jigsaw</b> as a NT service.</a></li>\r
+</ul>\r
+\r
+<h1>Using Servlets</h1>\r
+<ul>\r
+ <li><a href="User/servlets.html#what-are-servlets">What are servlets\r
+ ?</a></li>\r
+ <li><a href="User/servlets.html#compile-servlet">How do I compile jigsaw to\r
+ use the servlets ?</a></li>\r
+ <li><a href="User/servlets.html#install-servlets">How do I install a servlet\r
+ ?</a></li>\r
+ <li><a href="User/servlets.html#servlet-indexer">How do I configure a\r
+ servlet indexer?</a></li>\r
+ <li><a href="User/servlets.html#servlet-props">How can I setup the servlets\r
+ properties?</a></li>\r
+ <li><a href="User/servlets.html#load-servlets">How does Jigsaw load local\r
+ servlet classes ?</a></li>\r
+ <li><a href="User/servlets.html#remote-servlets">How can I load remote\r
+ servlets ?</a></li>\r
+</ul>\r
+You think your question about <b>Jigsaw</b> is worth entering this list, you\r
+have a better formulation for some of the answers ? Mail to <a\r
+href="mailto:jigsaw@w3.org">jigsaw@w3.org</a> !\r
+\r
+<h2><a name="purpose"></a>What's the purpose of <b>Jigsaw</b> ?</h2>\r
+<b>Jigsaw</b> is the new W3C reference server. Its main purpose is to\r
+demonstrate new protocol features as they are defined (such as <a\r
+href="/Protocols/">HTTP/1.1</a> or <a href="/PICS/">PICS</a>), and to provide\r
+the basis for experimentations in the field of server software (such as the\r
+provided MUX prototypical implementation).\r
+\r
+<h2><a name="download"></a>Where can I get <b>Jigsaw</b> ?</h2>\r
+You can download <b>Jigsaw</b> distribution file in various formats, and using\r
+either ftp or http:\r
+<dl>\r
+ <dt>Windows zip files (1.5Mo)</dt>\r
+ <dd><ul>\r
+ <li><a href="ftp://ftp.w3.org/pub/jigsaw/jigsaw.zip">FTP</a></li>\r
+ <li><a\r
+ href="http://www.w3.org/pub/WWW/Jigsaw/jigsaw.zip">HTTP</a></li>\r
+ </ul>\r
+ </dd>\r
+ <dt>UNIX gzip tar file (700Ko)</dt>\r
+ <dd><ul>\r
+ <li><a href="ftp://ftp.w3.org/pub/jigsaw/jigsaw.tar.gz">FTP</a></li>\r
+ <li><a\r
+ href="http://www.w3.org/pub/WWW/Jigsaw/jigsaw.tar.gz">HTTP</a></li>\r
+ </ul>\r
+ </dd>\r
+</dl>\r
+\r
+<h2><a name="java"></a>Why is <b>Jigsaw</b> written in Java ?</h2>\r
+<a href="http://www.javasoft.com/">Java</a> has a number of advantages that\r
+fit well with our purposes. It provides portable threads and garbage\r
+collection, allows for a very dynamic server architecture. It's ability to\r
+move code around may be use in future development to experiment with the\r
+mobile code concept.\r
+\r
+<h2><a name="slow"></a><b>Jigsaw</b> is written in Java, it must be really\r
+slow...</h2>\r
+No so true ! Check out the <a\r
+href="http://www.w3.org/pub/WWW/Jigsaw/User/Introduction/performance.html">performance\r
+evaluation of <b>Jigsaw</b></a>, which indicates that it performs at least as\r
+well as the CERN server.\r
+\r
+<h2><a name="Method-GET"></a>The admin server reply "Method GET not\r
+implemented.", how can I use it?</h2>\r
+The administration server does not use plain HTTP but a variant of it. The\r
+only tool available for now is an application called <a\r
+href="User/AdminTools.html">JigAdmin</a>.\r
+\r
+<h2><a name="jigsaw-indexing"></a>What is this <i>indexing</i> thing all about\r
+?</h2>\r
+To a normal HTTP web-admin, <b>Jigsaw</b>'s configuration process might look\r
+really strange...<a href="Programmer/design.html"><b>Jigsaw</b>'s design</a>\r
+emphasis two different processing stage in serving documents:\r
+<dl>\r
+ <dt>Indexing stage</dt>\r
+ <dd>When documents <i>enter</i> the Web</dd>\r
+ <dt>Serving stage</dt>\r
+ <dd>When documents are served to clients</dd>\r
+</dl>\r
+In short the rationale for separating these two stages is to make the\r
+<i>serving stage</i> as efficient as possible, by having the <i>indexing\r
+stage</i> prepare as much as possible the work. A document <i>enter</i> the\r
+WEB space the first time <b>Jigsaw</b> serves it; this happen behind the scene\r
+most of the time, and consist in creating a <i>resource</i> for the document\r
+to be served by querying a <i>resource factory</i>. The current resource\r
+factory can be configured to create various kind of resources based either on\r
+the file name extensions, or (in case of a directory) based on its name.\r
+\r
+<p>However, once a resource is created, it no longer reflects the settings of\r
+the resource factory (see the <a href="User/indexers.html">indexers</a>); in\r
+some sense the information gets <i>compiled</i> so that at serving time,\r
+processing overhead is reduced as much as possible.</p>\r
+\r
+<h2><a name="pass-directory"></a>How do I tie a resource to a directory not\r
+under my server root?<br>\r
+Contributed by <i>Sirilyan <sirilyan@io.com></i></h2>\r
+CERN server implemented this through the Pass directive, which let you map a\r
+server path to an absolute path on your file system. Jigsaw uses the\r
+org.w3c.jigsaw.resources.PassDirectory resource.\r
+\r
+<p>COOKBOOK METHOD: Create a new resource with <i>Add resources</i> in <a\r
+href="User/AdminTools.html">JigAdmin</a> at the location you want the new\r
+server path to exist. Assign whatever name you desire to the new resource, and\r
+assign <a\r
+href="Reference/org.w3c.jigsaw.resources.PassDirectory.html">org.w3c.jigsaw.resources.PassDirectory</a>\r
+for the class. Edit this new resource to change the pass-target attribute to\r
+the absolute path to the directory you want to serve.</p>\r
+\r
+<p>You may want to change the name attribute of the 'index' file in that\r
+directory to Overview.html. name and filename are two separate attributes in\r
+Jigsaw; this is also a poor man's (or a Win95/NT user's) symlink.</p>\r
+\r
+<p>Serving directories outside your server root may be a security risk.</p>\r
+\r
+<h2><a name="CGI-scripts"></a>How do I setup CGI scripts ?</h2>\r
+They are two ways to setup CGI scripts. The manual way requires that you\r
+describe each script to the server. Let's say your script's path relative to\r
+the server root is <tt>WWW/cgi-bin/myscript</tt>. You will first have to\r
+create an appropriate <a\r
+href="Reference/org.w3c.tools.resources.FileResource.html">org.w3c.tools.resources.FileResource</a>\r
+with a <a\r
+href="Reference/org.w3c.jigsaw.frames.CgiFrame.html">org.w3c.jigsaw.frames.CgiFrame</a>\r
+instance to wrap your script. See this <a\r
+href="User/resource.html">tutorials</a> to know how to create a resource in\r
+<b>Jigsaw</b>.\r
+\r
+<p>Then edit the newly created resource, and setup it's command line (the\r
+command line the server will use to run your script). Each line of the text\r
+field should represent one argument, the first one being the script full\r
+path.</p>\r
+\r
+<p>You can also register files of a given extension as scripts, by using a\r
+specialized <a href="User/indexers.html">indexer</a>. When required, you can\r
+even specify the interpreter to be run to execute the script (for example,\r
+under Windows 95, or NT).</p>\r
+\r
+<h2><a name="php3"></a>How can I use php3 in <b>Jigsaw</b> ?</h2>\r
+This is quite easy, the best way is to do it directly using an indexer. php3\r
+scripts will be handled as CGIs (so see the FAQ entry above).\r
+\r
+<p>You need first to compile php3 as a cgi interpreter, then configure the\r
+"php3" extension in your <a href="User/Indexers.html">indexer</a> using a <a\r
+href="Reference/org.w3c.tools.resources.FileResource.html">FileResource</a>\r
+and a <a href="Reference/org.w3c.jigsaw.frames.CgiFrame.html">CgiFrame</a>,\r
+like aforementionned. Then, in your <a\r
+href="Reference/org.w3c.jigsaw.frames.CgiFrame.html">CgiFrame</a>, set the\r
+"interpreter" field to your php binary, and "Generates Form" to true.\r
+<i>(Note, this will work with Jigsaw 2.0.2 and up)</i></p>\r
+\r
+<h2><a name="index"></a>How do I set the default document?</h2>\r
+With <a href="User/JigAdmin/Overview.html">JigAdmin</a> select the the <a\r
+href="Reference/org.w3c.jigsaw.frames.HTTPFrame.html">HTTPFrame</a> (or\r
+subclass) associated to the <a\r
+href="Reference/org.w3c.tools.resources.DirectoryResource.html">DirectoryResource</a>\r
+(or subclass) where you want to modify the default document. Then, set the "<a\r
+href="Reference/org.w3c.jigsaw.frames.HTTPFrame.html#index">index</a>" field\r
+to your default document (eg: index.html).\r
+\r
+<p><i>Note: Don't forget to commit and save your changes</i>.</p>\r
+\r
+<h2><a name="ssl"></a>Does Jigsaw support SSL?</h2>\r
+There was a SSL version of Jigsaw, done at <a\r
+href="http://jcewww.iaik.tu-graz.ac.at/">IAIK</a>. With Jigsaw 2.2.3, released\r
+on november 27th 2003, there is a native SSL implementation \r
+for the HTTP and WebDAV servers.\r
+\r
+\r
+<h2>What is the default Login Name and Password for JigAdmin?</h2>\r
+The default Login Name is: <b>admin</b>, the default Password is:\r
+<b>admin</b>.\r
+\r
+<p>This information is also available in the <a\r
+href="User/JigAdmin/running.html#auth">JigAdmin documentation</a>.</p>\r
+\r
+<h2><a name="extend"></a>How can I extend <b>Jigsaw</b> ?</h2>\r
+<b>Jigsaw</b> can be extended in a number of ways. Here are just three\r
+possible things you can play with, from the simplest to the complex ones:\r
+<ul>\r
+ <li>Writing new resource classes and new frame classes: you may want to read\r
+ the <a href="Programmer/writing-resources.html">tutorial</a> on this\r
+ subject before getting any further. You can think of this as being a n\r
+ efficient replacement for CGI scripts, although this is a much more\r
+ powerful environment to extend the server.</li>\r
+ <li>Writing new filter classes: if you want to experiment with specific\r
+ authentication needs, or if you require special logging formats. A <a\r
+ href="Programmer/writing-filters.html">tutorial</a> on writing new filters\r
+ is also available.</li>\r
+ <li>Hacking <b>Jigsaw</b>. Right now you can just override any of the\r
+ <b>Jigsaw</b> classes to replace its implementation. In the future, most\r
+ of the interesting things that you can do this way will be turned into\r
+ specific interfaces (as is already the case for logging right now).</li>\r
+</ul>\r
+\r
+<h2><a name="persist"></a>Why does <b>Jigsaw</b> implement its own persistence\r
+mechanism</h2>\r
+<b>Jigsaw</b> implements its own persistence mechanism while RMI already\r
+provides a way to serialize objects, why is it so, will it change ? What\r
+<b>Jigsaw</b> implements in the <tt>w3c.tools.store</tt> package is more then\r
+persistence. It provides both a way of serializing objects <i>and</i> a way of\r
+describing what and how the object will be dumped. The available\r
+meta-description of objects (that you can obtain through the\r
+<tt>getAttributes</tt> method of resources), is a central part of\r
+<b>Jigsaw</b> architecture, since it offers the ability to create generic\r
+resource editors. This is not likely to disappear.\r
+\r
+<p>However, <b>Jigsaw</b> persistence mechanism may be merged in the future to\r
+the RMI interface, just by providing an implementation of the\r
+<tt>readObject</tt> and <tt>writeObject</tt> method through its existing\r
+mechanism.</p>\r
+\r
+<h2><a name="client-hotjava"></a>How can I use HotJava on top of Jigsaw's HTTP\r
+client API ?</h2>\r
+<a href="http://www.javasoft.com/HotJava/index.html">HotJava</a> is Sun's Java\r
+based browser. If you want to experience an HTTP/1.1 compliant browser, you\r
+can run this browser on top of <b>Jigsaw</b>'s HTTP/1.1 compliant HTTP client\r
+API. To do so, you need to define the <tt>java.protocol.handler.pkgs</tt>\r
+property to <tt>w3c.www.protocol </tt>before launching HotJava. The best way\r
+to do so is to edit the HotJava property files.\r
+\r
+<p><b>Jigsaw</b>'s HTTP client API defines a number of other properties, if\r
+you are planing to use this setting, you should read the <a\r
+href="http://jigsaw.w3.org/Doc/Programmer/api/org/w3c/www/protocol/http/HttpManager.html">HttpManager</a>\r
+documentation to get the complete list of available properties. These will\r
+allow you to add caching, authentication, proxying and more to <a\r
+href="http://www.javasoft.com/HotJava/index.html">HotJava</a> !</p>\r
+\r
+<h2><a name="http-port"></a>Running <b>Jigsaw</b> on port 80 under UNIX</h2>\r
+As of release 1.0alpha5, <b>Jigsaw</b> can now run on port 80, without running\r
+as the <i>root</i> user. To implement that you need to install the relevant\r
+piece of native code. This C code has been compiled and tested under Solaris,\r
+porting it to a different platform/architecture should be pretty easy.\r
+\r
+<p>Follow the normal installation procedure, and try to run <b>Jigsaw</b> on a\r
+port greater than 1024. Once this work, stop <b>Jigsaw</b> (through\r
+<tt>/Admin/Exit</tt>), Make sure your LD_LIBRARY_PATH variable includes the\r
+directory containing <tt>libUnix.so</tt> (this is the <tt>Jigsaw/lib</tt>\r
+directory under the standard release).</p>\r
+\r
+<p>Select the user and group you want <b>Jigsaw</b> to run as. Make sure that\r
+user has read/write access to the entire <tt>config</tt> directory. Then, you\r
+just need to run <b>Jigsaw</b> through that special command line:</p>\r
+\r
+<p><tt>java org.w3c.jigsaw.Main -user <i>user</i> -group <i>group</i>\r
+<other-options></tt></p>\r
+\r
+<p>Where <i>user</i> and <i>group</i> should provide (resp.) the user and the\r
+group you want <b>Jigsaw</b> to run as.</p>\r
+\r
+<p><b>Warning</b>: As the underlying UNIX process will change personnality\r
+right after acquiring the socket, the form based <i>restart</i> button\r
+(available from the properties editor) will no longer work, since the process\r
+will no longer be able to allocate a socket on port 80. <br>\r
+Under such a setting, the only way to restart <b>Jigsaw</b> is to kill it\r
+(through <tt>/Admin/Exit</tt>) and restart it manually.</p>\r
+\r
+<h2><a name="chroot"></a>Chrooting <b>Jigsaw</b> under UNIX</h2>\r
+As of release 1.0alpha5, <b>Jigsaw</b> can now - under UNIX - be chroot'ed. If\r
+you try to do so, you are supposed to have some experiences with chroot'ing\r
+programs. We will assume that you already have a correct root to run a\r
+standard HTTP server and that you have read and understood the <i>Running\r
+Jigsaw on port 80 </i><a href="#http-port">FAQ entry</a>.\r
+\r
+<p>You need to install Java in that root (using whatever prefered way you\r
+want). To install <b>Jigsaw</b>, I would recommend using the following\r
+directory structure:</p>\r
+<dl>\r
+ <dt>/usr/local/jigsaw/classes</dt>\r
+ <dd>Should contain <b>Jigsaw</b>'s current distribution <i>jigsaw.zip</i>\r
+ class file</dd>\r
+ <dt>/usr/local/jigsaw/extensions</dt>\r
+ <dd>Is used to add extensions to the server while running, and should be\r
+ included in your CLASSPATH, <i>before</i> you start <b>Jigsaw</b>.</dd>\r
+ <dt>/usr/local/jigsaw/lib</dt>\r
+ <dd>Should contain <b>Jigsaw</b>'s native code support - ie\r
+ <i>libUnix.so</i> -(to make the appropriate UNIX system calls)</dd>\r
+</dl>\r
+Given that (don't forget to <i>symlink</i> the real <tt>/usr/local/jigsaw</tt>\r
+to the chroot'ed one), you should be able to reuse that script:\r
+<pre> #!/bin/sh\r
+# Jigsaw\r
+# $Id: FAQ.html,v 1.1 2010/06/15 12:27:24 smhuang Exp $\r
+# Jigsaw launcher\r
+ \r
+# LD_LIBRARY_PATH will be set to work *only* before chroot, by the java script\r
+# We add here, support for PATH as they appear to be after the chroot\r
+ \r
+CR_LD_LIBRARY_PATH=/usr/local/jigsaw/lib:/usr/local/java/lib/sparc:/usr/lib:/lib\r
+LD_LIBRARY_PATH=$CR_LD_LIBRARY_PATH:$LD_LIBRARY_PATH\r
+export LD_LIBRARY_PATH\r
+ \r
+# CLASSPATH needs two hacks: one to include jigsaw.zip before chroot, and\r
+# an other one to include everything after chroot\r
+ \r
+CLASSPATH=/0/w3c/abaird/sbroot/usr/local/jigsaw/classes/jigsaw.zip:/0/w3c/abaird\r
+/sbroot/usr/local/jigsaw/classes/servlet.zip:/0/w3c/abaird/sbroot/usr/local/jigs\r
+aw/classes/plus.zip:/0/w3c/abaird/sbroot/usr/local/jigsaw/extensions\r
+export CLASSPATH\r
+CR_CLASSPATH=/usr/local/jigsaw/classes/jigsaw.zip:/usr/local/jigsaw/classes/serv\r
+let.zip:/usr/local/jigsaw/classes/plus.zip:/usr/local/jigsaw/extensions\r
+CLASSPATH=$CR_CLASSPATH:$CLASSPATH\r
+export CLASSPATH\r
+ \r
+# Ready to run jigsaw, now:\r
+ \r
+cd /0/w3c/abaird/sbroot/jigsaw\r
+exec /usr/local/java/bin/java org.w3c.jigsaw.daemon.ServerHandlerManager $* -group n\r
+obody -user nobody -chroot /0/w3c/abaird/sbroot -root /jigsaw</pre>\r
+\r
+<h2><a name="Running"></a>Running Jigsaw as a NT service</h2>\r
+To be able to run Jigsaw as a service, you may use a tool allowing java\r
+programs to run as a service. You just have to make your choice in <a\r
+href="http://pharos.inria.fr/Java/search?term=s1:3428">this list</a>. Remember\r
+that the safest way to shut down Jigsaw is to use the <a\r
+href="User/JigAdmin/">administration interface</a> of <a\r
+href="User/jigkill.html">JigKill</a> <br>\r
+\r
+\r
+<p></p>\r
+</div>\r
+<!-- body -->\r
+\r
+<div class="footer">\r
+<hr noshade="noshade">\r
+<a href="mailto:jigsaw@w3.org">Jigsaw Team</a> <br>\r
+<span class="mini">$Id: FAQ.html,v 1.1 2010/06/15 12:27:24 smhuang Exp $</span>\r
+\r
+<p class="policyfooter"><font size="-1"><a\r
+href="/Consortium/Legal/ipr-notice.html#Copyright">Copyright</a> © 1999 <a\r
+href="http://www.w3.org">W3C</a> (<a href="http://www.lcs.mit.edu">MIT</a>, <a\r
+href="http://www.inria.fr/">INRIA</a>, <a\r
+href="http://www.keio.ac.jp/">Keio</a> ), All Rights Reserved. W3C <a\r
+href="/Consortium/Legal/ipr-notice.html#Legal Disclaimer">liability, </a><a\r
+href="/Consortium/Legal/ipr-notice.html#W3C Trademarks">trademark </a>, <a\r
+href="/Consortium/Legal/copyright-documents.html">document use </a>and <a\r
+href="/Consortium/Legal/copyright-software.html">software licensing </a>rules\r
+apply. Your interactions with this site are in accordance with our <a\r
+href="/Consortium/Legal/privacy-statement.html#Public">public </a>and <a\r
+href="/Consortium/Legal/privacy-statement.html#Members">Member </a>privacy\r
+statements.</font></p>\r
+</div>\r
+</body>\r
+</html>\r
projects / Benchmarks_CSolver.git / blobdiff