You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by kr...@k2d2.org on 2007/07/09 16:01:12 UTC
T5: Redirect after form submit - concerns
We are in the process of evaluating T5 and other frameworks to upgrade our existing trading applications from T3. We extensively use objects serialized to hidden fields (zipped and base64 encoded) to manage state because we absolutely have to support multiple browser windows in the same session. However, T5's redirect after form submit throws a wrench in the design since it forces the uses of session to store the data which fails with multiple browsers and creates unnecessary traffic in a clustered deployment. Why is this redirect necessary and is there a way of overriding/turning it off? If there is no way around it, T5 will not be an option for us to upgrade to. So I'm hoping to arrive at a solution.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5: Redirect after form submit - concerns
Posted by kranga <kr...@k2d2.org>.
If T5 already has the ability to persist fields into a form, then how to do
you retain those fields during a redirect? The URL is not long enough to
serialize every hidden field. So you'd be forced to store it in the session,
which breaks the scenario of multiple browser windows in the same session.
----- Original Message -----
From: "Howard Lewis Ship" <hl...@gmail.com>
To: "Tapestry users" <us...@tapestry.apache.org>
Sent: Monday, July 09, 2007 10:06 AM
Subject: Re: T5: Redirect after form submit - concerns
> T5 has the ability to to persist field properties onto the client (as
> zipped/based64) automatically. These show up as hidden form fields or
> extra query parameters. Not implemented yet is the ability to "scope"
> the data to only hidden form fields (but leave normal links unchanged)
> ... the API is present, there just isn't an implementation yet.
>
> On 7/9/07, kranga@k2d2.org <kr...@k2d2.org> wrote:
>> We are in the process of evaluating T5 and other frameworks to upgrade
>> our existing trading applications from T3. We extensively use objects
>> serialized to hidden fields (zipped and base64 encoded) to manage state
>> because we absolutely have to support multiple browser windows in the
>> same session. However, T5's redirect after form submit throws a wrench in
>> the design since it forces the uses of session to store the data which
>> fails with multiple browsers and creates unnecessary traffic in a
>> clustered deployment. Why is this redirect necessary and is there a way
>> of overriding/turning it off? If there is no way around it, T5 will not
>> be an option for us to upgrade to. So I'm hoping to arrive at a solution.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> --
> Howard M. Lewis Ship
> TWD Consulting, Inc.
> Independent J2EE / Open-Source Java Consultant
> Creator and PMC Chair, Apache Tapestry
> Creator, Apache HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5: Redirect after form submit - concerns
Posted by Howard Lewis Ship <hl...@gmail.com>.
T5 has the ability to to persist field properties onto the client (as
zipped/based64) automatically. These show up as hidden form fields or
extra query parameters. Not implemented yet is the ability to "scope"
the data to only hidden form fields (but leave normal links unchanged)
... the API is present, there just isn't an implementation yet.
On 7/9/07, kranga@k2d2.org <kr...@k2d2.org> wrote:
> We are in the process of evaluating T5 and other frameworks to upgrade our existing trading applications from T3. We extensively use objects serialized to hidden fields (zipped and base64 encoded) to manage state because we absolutely have to support multiple browser windows in the same session. However, T5's redirect after form submit throws a wrench in the design since it forces the uses of session to store the data which fails with multiple browsers and creates unnecessary traffic in a clustered deployment. Why is this redirect necessary and is there a way of overriding/turning it off? If there is no way around it, T5 will not be an option for us to upgrade to. So I'm hoping to arrive at a solution.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org