Hi Vlad, > > I have no idea. We are using the server with our own templating > > framework based on tDOM but I do not think this is something > > of general interest. > > I have light-weight templating i can extract and put into modules/tcl, > that will be one small file and will support OACS-style templating > where .adp and .tcl are define template. But it requires some work to be > extracted > from my "big" framework system.
I would also like to extract some functionality from our toolkit. It would be nice if there is a small toolkit with basic stuff like database abstraction, page and session management, authentication and basic permissions. I like the idea to rewrite it in a way so that it utilizes new naviserver functions like the c-cookie-api or database stuff (I read from Stephen?). In our framework we do not map and use the standard ADP-stuff, we use registered filters and procs and ns_adp_parse files, but it should be managable to rewrite it. > For public version in the future i would include as manu maintained > modules as possible. What do you think about a "contrib" directory (like in PostgreSQL or other packages): <QUOTE> The PostgreSQL contrib tree --------------------------- This subtree contains porting tools, analysis utilities, and plug-in features that are not part of the core PostgreSQL system, mainly because they address a limited audience or are too experimental to be part of the main source tree. This does not preclude their usefulness. Each subdirectory contains a README file with information about the module. </QUOTE> Something similar. This way it would be clearly stated that something is useful and/or experimental and/or just new (Message: "Give it a try"). Maybe this would be a place for a chroot-installation-script, like my first try here: http://www.kinetiqa.de/aolserver/ (But rewritten, it's a little bit old and worries about too many packages) Bernd.
