You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/11/28 22:28:43 UTC

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

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

Howard M. Lewis Ship closed TAPESTRY-1836.
------------------------------------------

    Resolution: Won't Fix
      Assignee: Howard M. Lewis Ship

You can use client persistence.  Look to minimize your client-side state.  What 255 character limit?

I do believe I've added a JIRA improvement issue, a way to store client-side state data on the server, and send a short key to the client side.  That's better in terms of bandwidth and security.

> 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