Return-Path: Delivered-To: apmail-tapestry-users-archive@www.apache.org Received: (qmail 95889 invoked from network); 2 Mar 2011 07:58:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Mar 2011 07:58:52 -0000 Received: (qmail 64149 invoked by uid 500); 2 Mar 2011 07:58:51 -0000 Delivered-To: apmail-tapestry-users-archive@tapestry.apache.org Received: (qmail 63841 invoked by uid 500); 2 Mar 2011 07:58:49 -0000 Mailing-List: contact users-help@tapestry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tapestry users" Delivered-To: mailing list users@tapestry.apache.org Received: (qmail 63833 invoked by uid 99); 2 Mar 2011 07:58:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 07:58:47 +0000 X-ASF-Spam-Status: No, hits=4.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RFC_ABUSE_POST,SPF_SOFTFAIL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of dugt3@hotmail.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 07:58:40 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1Pugwt-0003IB-OP for users@tapestry.apache.org; Tue, 01 Mar 2011 23:58:19 -0800 Date: Tue, 1 Mar 2011 23:58:19 -0800 (PST) From: Dany To: users@tapestry.apache.org Message-ID: <1299052699750-3406223.post@n5.nabble.com> In-Reply-To: References: <1299033042808-3405994.post@n5.nabble.com> Subject: Re: Tapestry 5.2 - Request data shared in different client browser MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Howard, Thanks for you soon reply. I have a doubt with repesct to you reply. If in tapestry 5.2 it works with only one instance (like in a servlet) then it is imposible to make the maching in a POJO/tml because this elements always is going to be a mutable objects (in the same way that a servlet with global variables). Then for this example (in tapestry 5.2) how do you make the machting the tml fields with java class without all users see the data bleed. Would you mind to provide an exanple for the correct use? Thanks in advance Kind Regards -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-Request-data-shared-in-different-client-browser-tp3405994p3406223.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org For additional commands, e-mail: users-help@tapestry.apache.org