[
https://issues.apache.org/jira/browse/ORCHESTRA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699345#action_12699345
]
Simon Kitching commented on ORCHESTRA-40:
-----------------------------------------
Could you describe some of the use-cases for this?
For transaction-oriented websites, back-buttons or "double clicking" of a page
can be nasty; it can cause operations to be done multiple times (eg buying
multiple copies of something) when the user didn't want that. The standard way
to detect back-button usage or "double clicks" on a web page is to have a
counter component in the page, and a matching counter in the http session. Both
get incremented on each request; if at the start of a request they don't match
then we have one of the above problems.
If I understand correctly, this patch adds a conversation-aware version of
this, which stores the counter in "the current conversation" for the submitting
page. But I'm not sure why this is useful. Why isn't a normal
non-conversation-aware token implementation sufficient?
Note that the Orchestra ViewController already has features to detect when a
page tries to use a conversation that does not exist (eg because it has been
invalidated at end of a transaction), and can redirect to the appropriate
"entry" page for the conversation.
> A transaction token component inspired by the struts transaction processor
> --------------------------------------------------------------------------
>
> Key: ORCHESTRA-40
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-40
> Project: MyFaces Orchestra
> Issue Type: New Feature
> Components: Conversation
> Affects Versions: 1.3.1
> Reporter: Bernd Bohmann
> Assignee: Simon Kitching
> Attachments: ORCHESTRA-40-CacheControl.patch,
> ORCHESTRA-40-TransactionToken.patch
>
>
> A transactionToken Component for orchestra inspired by the struts transaction
> processor.
> The transaction token is to be used for enforcing a single request for a
> particular transaction.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
