tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Todd <>
Subject Re: request for review: server/config discussion
Date Mon, 19 Jul 1999 20:58:43 GMT

	some tomcatDev discussions ... !fresh!

these are my thoughts as well and an area i'd like for us to
drill down on rsn. i think we're comfortable knowing what we
know about the entities which are likely to produce and use
the data ... what differentiates this, in my mind and i believe
yours as well, is that the "configuration service" should make
available in a protocol friendly means the configuration data
(or derived objects) and will singal to clients (most likely
passively) when a "data refresh" is required as the config
data has changed.

- james

"Craig R. McClanahan" wrote:
> James Todd wrote:
> > hi -
> >
> >         attached is a first cut at collecting the various
> >         thoughts surrounding a "pure java http server
> >         configuration" project.
> >
> I did not see this issue addressed so far (maybe it's more an issue for the server
> implementation itself), but I would like to see a mechanism where incremental changes
to the
> configuration information, such as adding a new Directory Path or changing an existing
> Maintainer (in the terminology of the Appendix example) are "absorbed" in to the running
> server without requiring a complete restart.  This may require architectural support
> the configuration data management module itself (as well as the API), to broadcast events
> changes occur.
> It should also go without saying that the results of this should be useful in configuring
> Tomcat components, not just the HTTP server :-).
> Craig McClanahan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message