Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 9060 invoked from network); 4 Jan 2006 19:10:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Jan 2006 19:10:34 -0000 Received: (qmail 17762 invoked by uid 500); 4 Jan 2006 19:10:28 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 17729 invoked by uid 500); 4 Jan 2006 19:10:28 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 17718 invoked by uid 99); 4 Jan 2006 19:10:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2006 11:10:27 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [206.123.111.90] (HELO mail.loukasmgmt.com) (206.123.111.90) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2006 11:10:26 -0800 Received: (qmail 6409 invoked by uid 510); 4 Jan 2006 13:10:09 -0600 Received: from unknown (HELO ?10.220.0.85?) (filip@loukasmgmt.com@198.212.148.166) by mail.loukasmgmt.com with SMTP; 4 Jan 2006 13:10:09 -0600 Message-ID: <43BC1D91.5030504@hanik.com> Date: Wed, 04 Jan 2006 13:10:09 -0600 From: Filip Hanik - Dev Lists User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Cutting Tomcat 5.5.15 tomorrow (Tuesday) References: <43BA6D34.9060608@apache.org> <43BBE8FB.1080606@hanik.com> <43BBEA03.7090607@apache.org> In-Reply-To: <43BBEA03.7090607@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N makes, sense, should be a simple check in the ReplicationValve.java code base, thanks for enlightening me Filip Remy Maucherat wrote: > Filip Hanik - Dev Lists wrote: > >> why would you replicate session data across contexts? cross context >> means different webapps, maybe I'm confused, but an app would never >> fail over from one webapp to a different webapp. > > > Right now, only the session for the webapp which first recieves the > request is checked for replication. If the request dispatches to > another webapp, modifications to the sessions in those webapps will > not be replicated right now. > > R�my > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org > For additional commands, e-mail: dev-help@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org