On Tue, Mar 11, 2003 at 12:05:35PM +0100, Michael Bell wrote:
> I think it is a good idea to restart here again because every interface 
> can be configured in a different way. So what do you think about the 
> following (I use ca as an example and OPENCADIR/etc/ is /etc/openca in 
> debian):
> 
> 1. OPENCADIR/etc/servers/ca.conf is the today's configuration
> 2. OPENCADIR/etc/servers/ca.conf.template which is a ca.conf but with 
> not replaced country
> 2. OPENCADIR/etc/servers.ca.xml is the future's configuration if we 
> switch to XML
> 3. we include in ca.xml a path like this openca/software_config/
> 4. in this section we build a list:
>    <option>
>        <name>country</name>
>        <value>DE</value>
>    </option>
>    We can parse XML really easy so it is no problem to load and use 
> these options.
> 5. we build a script which reads the original ca.conf.template and 
> create the new ca.conf

You mean it tages ca.xml + ca.conf.template and outputs ca.conf?

> 6. we create a function which can translate files (perhaps we include it 
> to OpenCA::TRIStrateCGI)

> Any comments to these ideas? Perhaps a special character is not enough 
> for the variable so what do you think about a special descriptive prefix?

Sounds good to me.

I am not really sure on this last issue, do you plan to have static
translation of the files, and save the results somewhere on disk, or do
you plan to have dynamic translation, and translate on every load?

Alternatively (if thats not enough options already), you could go
somewhere inbetween, ie translate the files and cache them somewhere.
-- 
Brian May <[EMAIL PROTECTED]>


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-devel

Reply via email to