The Acme.serve HTTP server that I am about to upload to SourceForge
(their CVS is way mopre complicated than Apache's) contains a config.xml
line:
<root-location>c:/download/</root-location>
This is the root of the HTTP file system as mapped to the server's
underlying file system. Two things jump out at you 1) it's a windows
specific file location and 2) it's my downloads directory (not everyone
has that dir, nor would want to serve it).
Should we in fact have some deferred configutration concepts. The
Avalon .sar installer spots them and prompts for actual values :
<http-server>
<port>8080</port>
<bind>127.0.0.1</bind>
<root-location deferred-code="root-locn"/>
<helloworldhandler>
<connectiontimeout>360000</connectiontimeout>
</helloworldhandler>
</http-server>
<deferred-configuration>
<root-locn type="filesystem-path">
<default>c:/downloads/</default>
<message>The Webserver's index.html page will map to a local file
system direcory. That directory and below will be served to all
browsers</message>
</root-locn>
</deferred-configuration>
The default ConfigurationPrompter could be console. Another
implementation could be some "message queue" concept. Other people may
choose to resolve them prior to deployment, with a command line
configuration resolver. Then again, maybe .sar deployment is not meant
to be a no-brainer, it's supposed to be a high-art "assembler" duty.
Thoughts?
- Paul H
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
