httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vincent Janelle <>
Subject Re: environment patch
Date Fri, 09 Jul 1999 03:19:57 GMT
Actually, although I don't want to mention some of the competetion ;) 
Roxen challenger does this already..

An example.. lets see..


In this case, <a> is for the server connections.

the first <int> is for the port to run on(
if you want to see the roxen docs.. Included as a server setup)

the <str>http</str> is what protocol to use.  In this case, http.  Other
things like SSL3 are supported like..
    <str>cert-file /usr/local/roxen/server/demo_certificate.pem

the ANY is the IP address directive... In this case, roxen opens port
5000 on all bound ips.

</a> closes the mix.

This makes it possible to make complex graphical interfaces(roxen 1.4
actually includes comments by default to explain what things are).. But
they're a bitch to learn.

> As a rough guess, I would recommend that we pass a module its
> configuration element, and it can then process the child elements and
> any relevant attributes.
> For example, let's say that we have the following XML config:
> <alias>
>   <location>/gstein</location>
>   <directory>/home/gstein/htdocs</directory>
> </alias>

If life is merely a joke, the question still remains: for whose
-- --UIN 23939474

View raw message