tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hls...@comcast.net
Subject Re: Why so many synthetic properties?
Date Thu, 18 Dec 2003 21:06:54 GMT
It's all about page pooling ... ensuring that properties are reset to null or initial values
at the end of the request cycle.
> The question I asked earlier about why AbstractFormComponent was changed to
> use a synthetic form property makes me wonder about this in general - why
> does Tapestry 3 use so many synthetic properties?
> 
> Is it just a matter of eating our own dog food? ie. "because we can".
> 
> It seems to me that the framework itself would be better off if it didn't
> require any runtime enhancing.  Are there cases where the runtime enhancing
> provides some functional benefit and is actually _needed_?
> 
> R
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> 

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


Mime
View raw message