[
https://issues.apache.org/jira/browse/TAPESTRY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535888
]
kron bars commented on TAPESTRY-1836:
-------------------------------------
The load balancer is usually sticky-session for clusters but the flash will
cause short-lived data to be replicated in the cluster - which would result in
a lot of unnecessary session synchronization of no value. Is there a way to
prevent the redirect? It doesn't seem right for a framework to dictate such an
operation for every form submit.
> 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
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
