click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CLK-732) Add Page option to serialize access
Date Fri, 21 Jan 2011 11:55:43 GMT

     [ https://issues.apache.org/jira/browse/CLK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bob Schellink updated CLK-732:
------------------------------

    Fix Version/s:     (was: 2.3.0-RC1)

While implementing this I've realized that by using a page property to flag a page access
as serialized it also means the page constructor won't benefit from the lock, leading to inconsistent
results. Removing from roadmap for now. An alternative implementation will have to specify
the serialized page access outside the page eg. click.xml or have a global property serializing
all access to all pages for a given user.

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


Mime
View raw message