Dossy Shiobara said: > I do agree. In 2005, I'd love to see the start of an AOLserver Web > Development Kit (WDK), especially based around my AOLserver Standard Tag > Library that I'm working on. That'd be fantastic. One thing I have been thinking of lately, is a new way of deploying application, very similar to the way J2EE does it:
Basicaly, have a directory structure like: appname appname/lib (Tcl libraries) appname/pages (obvious) appname/resources (non-pageroot files - translations, xslt, etc) appname/config.tcl (configuration directives for this app) This could then be configured in the main config file as application to use, including the root url. So you could tie, say, OpenACS to "/acs", or simply "/" and (the imaginary) nsWiki to "/wiki". Using the multiple thread pools and virtual server functionality, you could even completely seperate applications in one server for tuning and security. A set up like this would make it as easy to add an AOLserver application to your existing server as it is to, for instance, install Gallery in Apache. To really make this work, AOLserver should have a standard security API that all applications can rely on. This can be a simple as a user/group/role set-up. As it is defined as an API, many implementations can exists; a most basic one with XML files for the user info. This would still make applications responsible for their own security, by checking users and roles using API calls (ns_sec isloggedin, ns_sec hasrole admin, etc), but at least every application can do it in the same way. Just some thoughts... Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
