Return-Path: Delivered-To: apmail-click-dev-archive@www.apache.org Received: (qmail 93476 invoked from network); 21 Nov 2010 03:03:03 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 Nov 2010 03:03:03 -0000 Received: (qmail 85537 invoked by uid 500); 21 Nov 2010 03:03:35 -0000 Delivered-To: apmail-click-dev-archive@click.apache.org Received: (qmail 85478 invoked by uid 500); 21 Nov 2010 03:03:34 -0000 Mailing-List: contact dev-help@click.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@click.apache.org Delivered-To: mailing list dev@click.apache.org Received: (qmail 85471 invoked by uid 99); 21 Nov 2010 03:03:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Nov 2010 03:03:34 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Nov 2010 03:03:33 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oAL33Dr4012977 for ; Sun, 21 Nov 2010 03:03:13 GMT Message-ID: <24762633.218351290308593450.JavaMail.jira@thor> Date: Sat, 20 Nov 2010 22:03:13 -0500 (EST) From: "Bob Schellink (JIRA)" To: dev@click.apache.org Subject: [jira] Created: (CLK-732) Add Page option to serialize access MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Add Page option to serialize access ----------------------------------- Key: CLK-732 URL: https://issues.apache.org/jira/browse/CLK-732 Project: Click Issue Type: Improvement Reporter: Bob Schellink When accessing data in a session there is always the possibility to concurrent access eg. user clicks a link or button twice in quick succession. With Ajax this possibility gets higher. Would be nice if we can have a Page option to serialize Page access -> setSerialize(true); This would ensure that a page is accessed from only one request at a time. One problem with this is that if a browser makes an Ajax connection which takes a long time to complete, other requests would be blocked lowering the application responsiveness. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.