> -----Original Message----- > From: NormW > > Hmmm.... > It seems your proposal has left everyone speechless.... which could > mean either +1 or +0 perhaps... > Norm >
It's probably +0 thought :) Really, I think it's a good solution, that doesn't change the overall appearance of the current implementation. The current one can be embedded as const char * string parsed, but you may have an external file for what ever format you like. The two directives to the [status] should be added and those are 'template' and 'contentType'. Without it's presence the default one will get displayed. I'm using the code for a custom mod_dir that generates the xml directory listings, and it works good enough. It is useful in any situation where you have mixture of key-value pares combined with the collection of key-value pairs generated using loops. MT. > > > > If the appropriate solution is to have a template file that > can generate > > what ever content then I have a solution. > > http://jakarta.apache.org/~mturk/strproc.zip is a simple > state template > > engine with only 13k of code. > > You can define loop callbacks and have a content what ever > you like html, > > txt or xml. > > > > If the template file is the acceptable solution then I can help you > > integrate that. > > The gain is to have a single codebase that can generate any > type of a > > content. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
