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 Tue, 20 Jul 1999 21:46:07 GMT
Ben Laurie wrote:

> Much as I like the idea of notifying config changes, I think it is
> likely to lead to trouble. Here's the problem in a nutshell: either you
> notify in detail what the changes are, in which case we are looking at
> horrendous complexity and likely lots of interesting failure modes, or
> you just say "it's changed" in which case you only need a single module
> that requires a restart (canonical example: Apache listeners - these
> cannot change without a restart) and every change gives you a restart
> anyway.

this is why i'm presently (informally in this list and a small
bit more formally in the discussion doc) piloting the idea of
"passive" notification from the perspective of the config service.

it could be that an api is provided via the service to "check"
the freshness (born on date) of the data and leave it up to
the client (eg server) to do with what it may with the results.
another passive means might be to throgh some sort of exception
indicating that "data you've obtained from me has since been

this just feels right at this stage in the game. we could up
the ante a bit and consider an active notification scheme whereby
the config service persists a reference to clients (listeners)
and broadcasts changes accordingly.

i'm a proponent of "passive" notification as 1) it is likely
better then what is available today, 2) the api and subsequent
implementations are rather trivial and 3) it doesn't too tightly
couple subscribers of a service nor mandate too much behaviour.

hope this helps,

- james

View raw message