Logo Search packages:      
Sourcecode: caudium version File versions


/* -*- Pike -*-
 * $Id: performance.h,v 2003/07/24 09:10:05 kiwi Exp $
 * Performance related defines. Also used to enable/disable Roxen
 * compat stuff that's disable for performance reasons.


/* Define this for maximum performance. Handy for benchmarking. */

/* #define MAX_PERFORMANCE */

/* Enable extra Roxen 1.3 compatibility. This is mainly performance issues.
 * See the file README.compatibility for a complete list of changes related
 * to this define.


/* Enable support for HTTP/0.9. This is an extremely minor optimization. If
 * you need HTTP/0.9, enable this one. Will not work with http2.pike...

#undef SUPPORT_HTTP_09

/* Enable the request memory cache. This greatly speeds up requests. It's
 * worth it for most sites. Only used by the experimental http2 protocol.

#ifndef NO_RAM_CACHE

/* Do we want module level deny/allow security (IP-numbers and usernames). 
 * This is a minor optimzation. You can uncomment this for stupid servers
 * where module level security isn't needed.


/* If this is disabled, the server won't parse the supports string. This might
 * make the server somewhat faster. Since supports parsing is cached, the
 * difference should be rather slim. Still, if you don't need the supports,
 * uncomment this define.


/* Define this if you don't want Caudium to use DNS. Note: This is a
 * minor speed optimization It's mainly used to reload network / dns
 * server load on busy servers. Please note that option turns off ALL
 * ip -> hostname and hostname -> ip conversion. Thus you can't use if
 * if you want to run a proxy or domain/host name based security. See

#undef NO_DNS

# ifndef NO_DNS
#  define NO_DNS
# endif

/* This option turns of all ip->hostname lookups. However the
 * hostname->ip lookups are still functional. This _is_ usable
 * if you run a proxy, but still breaks host based authentication.


/* Should we allow the config interface to lookup the hostnames of
 * all ip-addresses on the machine? This is the default, but if your
 * machine has a large number of virtual interfaces, we recommend that you
 * disable this feature. The reason being that it takes a long time to do the
 * ip -> hostname lookups. It's done for cosmetical reasons only.


/* Should we use sete?id instead of set?id?.
 * There _might_ be security problems with the sete?id functions.


/* Compatibility with some Really Old Server. Quite possibly not even
 * used at all anymore.
#undef COMPAT

 * Should support for URL modules be included? This includes the
 * htaccess module for example.  
# define URL_MODULES

/* Basically, should it be o.k. to return "string" as a member of
 * the result mapping? This is only for compability.
 * Normally: ([ "data":long_string, "type":"text/html" ]), was
 * ([ "string":long_string, "type":"text/html" ]), please ignore..
 * Do not use this, unless you _really_ want to make your
 * modules unportable :-)

 * Caudium 1.2 has a new error handler that allow you to create more
 * sexy error handler that the one used in Caudium 1.0 or Roxen 1.3.xx.
 * Because of XML-Compliant Parser is based on Pike's Parser.HTML that
 * has the main problem to fails to parse so HTML standart tags and/or
 * comment, sometime a 404 error is break the parser and give a 500 error
 * (internal server error) when XML-Compliant parser is used.
#ifndef DISABLE_NEW404
# define ENABLE_NEW404

 * Load all configurations (virtual servers and their modules) at
 * Caudium startup.
 * This is not enabled for performance reasons (eg Caudium with lots of
 * virtuals servers that are mostly unused.).


Generated by  Doxygen 1.6.0   Back to index