Looking at the conceptual diagrams at Apache Server site, httpd should be able to do this if it does not rely on file extensions to decide on the module to handle the entire template. It will need a mechanism to identify the handlers based on the parts of the template. Then it can as complex as filtering & chaining etc.
All said, this definitely falls in the scope of httpd.... Best Regards, Nagu. On Mon, Jul 23, 2012 at 9:40 PM, Massimo Manghi <massimo.man...@unipr.it>wrote: > A multi-language content generation module... I can hardly think of a such > a beast, but I could be a stubborn conservative. > > It would work if content generation modules worked like filters, > outputting down the filter chain for the other module to parse their > embedded code. I make out dreadful problems ahead and uncertain benefits, > considering also the many alternatives you have today. > > -- Massimo > > > > On 2012-07-23 6:08, Nagarajan Chinnasamy wrote: > >> >> This point leads me to the imagination of having a template that has >> all different things embedded (xml, tcl code, php code etc.). This may >> need a super-template-processing-**module as an apache module that >> dispatches a <?xxx block to the right template-processing-module based >> on configuration directives. >> >> Best Regards, >> Nagu. >> >> >
