Return-Path: <troy@glory.besmarter.com>
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 24459 invoked from network); 20 Jul 1999 22:37:11 -0000
Received: from glory.besmarter.com (qmaild@199.227.77.69)
  by apache.org with SMTP; 20 Jul 1999 22:37:11 -0000
Received: (qmail 32153 invoked by uid 1020); 20 Jul 1999 22:37:08 -0000
Date: Tue, 20 Jul 1999 18:37:08 -0400
From: Troy Poppe <troy@usite.net>
To: tomcat-dev@jakarta.apache.org
Subject: Re: request for review: server/config discussion
Message-ID: <19990720183708.B31037@usite.net>
References: <DC37797EB8C3D21197280008C74C893DF119A3@USAMCMS2>
 <3794DCB6.D7A9872E@eng.sun.com> <3794E650.D038BB6A@algroup.co.uk>
 <3794EE1F.A98D643B@eng.sun.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <3794EE1F.A98D643B@eng.sun.com>;
 from James Todd on Tue, Jul 20, 1999 at 02:46:07PM -0700

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

I like this idea of the server becoming the client for its own
configuration (that is what you are saying right? :)).  Meta-configuation
perhaps?

- Troy