You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2014/04/08 16:36:17 UTC
[jira] [Commented] (DELTASPIKE-564) optional double submit
prevention
[ https://issues.apache.org/jira/browse/DELTASPIKE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963039#comment-13963039 ]
Gerhard Petracek commented on DELTASPIKE-564:
---------------------------------------------
i'll also prototype a version specific to jsf
> optional double submit prevention
> ---------------------------------
>
> Key: DELTASPIKE-564
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-564
> Project: DeltaSpike
> Issue Type: New Feature
> Components: JSF-Module, Servlet-Module
> Affects Versions: 0.6
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
> Fix For: 0.7
>
> Attachments: DELTASPIKE-564_first_draft.patch
>
>
> duplicated post-requests shouldn't get processed
> #1 post requests need to get synchronized (per session)
> #2 post requests need to consume an existing request-token
> #3 re-render the page in case of a duplicated post-requests (+ skip full processing)
> #4 in case of jsf: reset the previous request-token(s) per window in case of a get-request (because a new page isn't aware of them)
> #5 reset the request-tokens in case of a duplicated post-requests >per window<, since the page will get re-rendered with a new token
> #6 don't create request-tokens in case of resource-requests
> #7 ignore duplicated jsf-ajax requests (they shouldn't happen, since the jsf-js implementation has to process them sequentially)
--
This message was sent by Atlassian JIRA
(v6.2#6252)