Return-Path: 
 <dev-return-78978-apmail-tomcat-dev-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-dev-archive@www.apache.org
Received: (qmail 40129 invoked from network); 2 Mar 2007 15:19:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 2 Mar 2007 15:19:29 -0000
Received: (qmail 94032 invoked by uid 500); 2 Mar 2007 15:19:34 -0000
Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org
Received: (qmail 93623 invoked by uid 500); 2 Mar 2007 15:19:32 -0000
Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@tomcat.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@tomcat.apache.org>
List-Post: <mailto:dev@tomcat.apache.org>
List-Id: <dev.tomcat.apache.org>
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Delivered-To: mailing list dev@tomcat.apache.org
Received: (qmail 93612 invoked by uid 99); 2 Mar 2007 15:19:32 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 07:19:32 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of yoavshapira@gmail.com
 designates 72.14.204.232 as permitted sender)
Received: from [72.14.204.232] (HELO qb-out-0506.google.com) (72.14.204.232)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 07:19:21 -0800
Received: by qb-out-0506.google.com with SMTP id d8so743784qbc
        for <dev@tomcat.apache.org>; Fri, 02 Mar 2007 07:19:00 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=DgvLSMF+LvcQcg48K3wvUabu9ySOxEPchf/e45ChehgZA6Dm5sshAcih9I7ZSZhuShDWuHXmi3rVjlaVX6u5zN3oJoffl8I7lWsM1wwSkhDA1fIGayzEJ1oQbzysx8mQ9p3zV5WiG3pBDXQsYYrQCPNXaMnmZB5oZAfpEbIwllg=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=V3aCrClyRHwER7KCHIbNGaMeSRtYRjl586mr+3srz/tnwSt9PVCYCs4gVhg05XJFDIYlYDjHoVrnKrHBYhYOv0MB79/f97omMCFCAS42HqdWeNuqJxfMMcBcnrhlY9Lt8qoTg9luBZY0812jvJqJHuHL/gda7Y55hBrD1bh9LN4=
Received: by 10.114.168.1 with SMTP id q1mr241862wae.1172848739793;
        Fri, 02 Mar 2007 07:18:59 -0800 (PST)
Received: by 10.114.59.16 with HTTP; Fri, 2 Mar 2007 07:18:59 -0800 (PST)
Message-ID: <db94f1a0703020718q5079eebic01d8b6f230f9fa@mail.gmail.com>
Date: Fri, 2 Mar 2007 10:18:59 -0500
From: "Yoav Shapira" <yoavs@apache.org>
Sender: yoavshapira@gmail.com
To: "Tomcat Developers List" <dev@tomcat.apache.org>
Subject: Re: reload on demand
In-Reply-To: <loom.20070302T160328-812@post.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <loom.20070301T075216-184@post.gmane.org>
	 <405A8DA9BECB2940B758D3521DFCF6C00592CF@sparus-exchange.ad.sparus.fr>
	 <loom.20070301T163551-859@post.gmane.org>
	 <db94f1a0703010754n6864b0c1y7228a5c10a814f6a@mail.gmail.com>
	 <loom.20070302T021116-940@post.gmane.org> <45E7943C.80501@hanik.com>
	 <loom.20070302T044511-647@post.gmane.org> <45E8323A.9020506@hanik.com>
	 <loom.20070302T160328-812@post.gmane.org>
X-Google-Sender-Auth: 93b9f4fcdef18807
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

On 3/2/07, Kent Tong <kent@cpttm.org.mo> wrote:
> Filip Hanik - Dev Lists <devlists <at> hanik.com> writes:
>
> > sounds like you want the cake and eat it too, follow Yoav's suggestion,
> > and write a macro so that everytime you update a class you touch a
> > watched resource after the update has been complete
>
> I really don't understand. What's wrong with reloading a changed webapp
> whenever it is accessed?

The general idea is to reload an app when you know it needs to be
reloaded, not when it's accessed, so as to minimize delays as seen by
the users.  It's a basic principle of designing for performance.
However, there's nothing written in stone that says you can't do what
you want: go write the code and have a blast with it ;)  That's part
of the fun of open-source software...

Yoav

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org