[jira] Reopened: (TAPESTRY-1836) Redirect after post causes issues with maintaining client side persistence and forces use of session

["kron bars (JIRA)" <de...@tapestry.apache.org>]

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

kron bars reopened TAPESTRY-1836:
---------------------------------


Perhaps the original description is not clear:

In the simple scenario where you have a form that posts to a page and you have client-side data persisted in the form, when you post the form, due to the server side redirect, the state that was posted to the server, if it needs to continue to be persisted (say due to validation failure of the form keeping user in the same page), then due to the redirect-after-post feature of T5, we are forced to either save that state on the server in "flash" session or persistent session. 

We cannot use persistent session because of the nature - complex financial apps wherein users invariably open multiple browser windows into the same session. 

The flash session strategy is terrible in a large clustered deployment. We had a similar setup for a different purpose and the cluster replication traffic because of the flash session was too much.

Therefore we need a way to maintain the client state in the client through the redirect. IMHO a major operation like redirect should not be done by an underlying framework. Please reconsider and allow for override of redirect.

> Redirect after post causes issues with maintaining client side persistence and forces use of session
> ----------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1836
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1836
>             Project: Tapestry
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.5
>            Reporter: kron bars
>            Assignee: Howard M. Lewis Ship
>
> We have a lot of pages that serialize objects into the form (gzip + base 64). This is necessary because we want to absolutely avoid using the session (clustering concerns and multiple-browsers with same session concerns). In T5, a form post results in a redirect. So if serialized state is present in the form, the redirect will necessarily cause that to be lost (the URL with its 256 character limitation is not an option to pass the state through). Thus we are forced to hold the state in session. This leads to major problems when the user has multiple browsers open into the same session (which they always do given the nature of our application).
> An option is required to disable the redirect after form post.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org