Roxen.git / server / base_server / configuration.pike

version» Context lines:

Roxen.git/server/base_server/configuration.pike:1:   // This file is part of Roxen WebServer.   // Copyright © 1996 - 2001, Roxen IS.   //      // @appears Configuration   //! A site's main configuration    - constant cvs_version = "$Id: configuration.pike,v 1.528 2002/12/10 18:31:07 mast Exp $"; + constant cvs_version = "$Id: configuration.pike,v 1.529 2003/01/13 15:16:40 mast Exp $";   #include <module.h>   #include <module_constants.h>   #include <roxen.h>   #include <request_trace.h>   #include <timers.h>      #define CATCH(P,X) do{mixed e;if(e=catch{X;})report_error("While "+P+"\n"+describe_backtrace(e));}while(0)      // --- Locale defines ---   //<locale-token project="roxen_start"> LOC_S </locale-token>
Roxen.git/server/base_server/configuration.pike:3429:   <tr valign='top'><td>2.4&nbsp;&nbsp;</td>    <td>Corresponds to Roxen WebServer 2.4. This version is also    commonly known as 3.2 - the version number that applies to the    release of Roxen CMS which contains Roxen WebServer 2.4.</td></tr>   <tr valign='top'><td>2.5&nbsp;&nbsp;</td>    <td>Corresponds to no released version. This compatibility level is    only used to turn on some optimizations that have compatibility    issues with 2.4, notably the optimization of cache static tags in    the &lt;cache&gt; tag.</td></tr>   <tr valign='top'><td>3.3&nbsp;&nbsp;</td> -  <td>Corresponds to Roxen WebServer 3.3.</td></tr> +  <td>Corresponds to Roxen 3.3.</td></tr> + <tr valign='top'><td>3.4&nbsp;&nbsp;</td> +  <td>Corresponds to Roxen 3.4.</td></tr>   </table></p>")));       set ("compat_level", roxen.__roxen_version__);    // Note to developers: This setting can be accessed through    // id->conf->query("compat_level") or similar, but observe that that    // call is not entirely cheap. It's therefore advisable to put it in    // a local variable if the compatibility level is to be tested    // frequently. It's perfectly all right to do that in e.g. the    // module start function, since the documentation explicitly states    // that a reload of all modules is necessary to propagate a change