On Mon, 20 Feb 2006 14:52:12 +0000, Bas Scheffers <[EMAIL PROTECTED]> wrote:

>The goal would be to have simple deployable application modules, quite
>like a "WAR" file in J2EE. Let's codename it "AOLserver Application
>Package", or AAP for short. (yes, that is Dutch for "monkey")
>
>This would give the advantage that it would be easy to deploy any open
>source applications written for AOLserver without having to copy loads
>of files into the right location or do much editing the global nsd.tcl.
>Just drop it in and go. You could even do it the Tomcat way; just drop
>the .aap file in the "applications" directory and it will unpack and
>bind it to a url automatically.

Could AOLServer use tcl's vfs layer to directly mount say, a zipfile or a
tclkit file?  This would make for a very nice deployment method and works
well elsewhere.  

Since the configuration file is a tcl program, it could include
configuration from other files.  Maybe an AAP package could include a file
that is to be inserted into the main config.tcl at server startup to load
whatever modules and database pools it needs.  The big downside is it would
need a server restart to load a new package.

Whatever you come up with, please don't have the configuration in a few
dozen xml files ala tomcat.  Just because everyone else does it that way
doesn't mean it's a good way to do it.  

-J


--
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.

Reply via email to