You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Skriloff, Nicholas" <Sk...@darden.virginia.edu> on 2006/01/11 22:22:29 UTC
RE: Xtile: Repsonse hanging
When tapestry renders a page, is there any difference between
public abstract boolean getUserLoggedIn();
public abstract void setUserLoggedIn(boolean userLoggedIn);
AND
private boolean userLoggedIn;
public boolean getUserLoggedIn(){
return userLoggedIn;
}
public void setUserLoggedIn(boolean userLoggedIn){
this.userLoggedIn = userLoggedIn;
}
?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Xtile: Repsonse hanging
Posted by Robert Zeigler <ro...@scazdl.org>.
Yes. The former will let tapestry work its magic to ensure that
properties are properly cleared when the page is returned to the pool so
that other users don't access user-specific information.
The latter version won't.
Use the former.
Robert
Skriloff, Nicholas wrote:
>When tapestry renders a page, is there any difference between
> public abstract boolean getUserLoggedIn();
> public abstract void setUserLoggedIn(boolean userLoggedIn);
>
>AND
> private boolean userLoggedIn;
>
> public boolean getUserLoggedIn(){
> return userLoggedIn;
> }
> public void setUserLoggedIn(boolean userLoggedIn){
> this.userLoggedIn = userLoggedIn;
> }
>?
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org