T5: How to handle caching for applications in multi-user environments

[Thomas Zenglein <Th...@rrze.uni-erlangen.de>]

Hi,

we encountered the situation where users authenticate in a web application, then using a web form to send mail to certain e-mail addresses. 
The T5 app for that resides under the same URI (here: https://some-server/mymailer/start). Certain web form elements (e.g. 1-line input fields) are prepopulated with data, depending on the URL GET parameters passed to the T5 app (e.g.  https://some-server/mymailer/start?a=b&c=d) and on session data.

Now: with different parameters, the web form values remain the same (!), resulting in the display of previously entered information for the next authenticated user using the T5 app 
=> I need to get rid of this obvious caching issue, but currently have no idea how.

I tried passing
-Dorg.apache.tapestry.disable-caching=true
to the Tomcat binary for start-up - unfortunately didn't help.

The env is: T 5.0.6, tomcat-5.5.23, SLES 10, Java 1.5.0_13 - on the server.
Browsers hitting the T5 app were IE 6.0.2900, FF 2.0.0.11.

Any of you guys have any idea how to prevent a T5 page from using its "cached version" for display? I feel I'm missing sth obvious but also feel pretty much stuck :(

Thanks for any pointers,
Thomas. 


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

Re: T5: How to handle caching for applications in multi-user environments

[Robert Zeigler <ro...@scazdl.org>]

Hi Thomas,

I don't have any issues in T5 like what you describe.

How are you storing the request values? I assume you're putting them  
into page fields?

A few things to check:
1) Your page fields need to be private
2) If you're trying to store the values in the httpsession, make sure  
you're using the @Persist annotation, rather than the @Retain  
annotation.

Robert

On Feb 4, 2008, at 2/412:55 PM , Thomas Zenglein wrote:

> Hi,
>
> we encountered the situation where users authenticate in a web  
> application, then using a web form to send mail to certain e-mail  
> addresses.
> The T5 app for that resides under the same URI (here: https://some-server/mymailer/start) 
> . Certain web form elements (e.g. 1-line input fields) are  
> prepopulated with data, depending on the URL GET parameters passed  
> to the T5 app (e.g.  https://some-server/mymailer/start?a=b&c=d) and  
> on session data.
>
> Now: with different parameters, the web form values remain the same  
> (!), resulting in the display of previously entered information for  
> the next authenticated user using the T5 app
> => I need to get rid of this obvious caching issue, but currently  
> have no idea how.
>
> I tried passing
> -Dorg.apache.tapestry.disable-caching=true
> to the Tomcat binary for start-up - unfortunately didn't help.
>
> The env is: T 5.0.6, tomcat-5.5.23, SLES 10, Java 1.5.0_13 - on the  
> server.
> Browsers hitting the T5 app were IE 6.0.2900, FF 2.0.0.11.
>
> Any of you guys have any idea how to prevent a T5 page from using  
> its "cached version" for display? I feel I'm missing sth obvious but  
> also feel pretty much stuck :(
>
> Thanks for any pointers,
> Thomas.
>
>
> ---------------------------------------------------------------------
> 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