Auto-generation of output files

System

With just a couple of hours of development (about 200 lines of DCT, FormAPI and Perl CGI) I have a functional prototype that allows the user to select the output directory for a DCR using a DCT select list, which means as long as a DCR only generates output files to one directory I can completely automate generation for the user (get the output file directory from the DCR, base the output file name on the DCR name, get the extension from templating.cfg, etc.).

Firstly let me say that because it's this easy I find it frustrating that Interwoven doesn't provide the functionality in the base product, even if some customers would choose not to use it.

I would be happy to share the code with anyone who would be willing to help me flesh it out - for instance I haven't determined how to prevent the user from being able to generate to specific directories. I also wonder what other issues I should consider, and whether I should even bother with this functionality due to TeamSite 6 (will it finally provide this functionality?). I also seem to remember posts by Interwoven pushing developers towards Java instead of Perl/CGI - is there any reason I should do this with a JSP or servlet instead of a CGI? I don't see where ContentServices or OpenAPI would help because I'm not calling any Interwoven CLTs/APIs in the CGI - just reading from the filesystem.

Any input would be appreciated...