On Thursday, September 18, 2003, at 05:04 AM, deelan wrote:
> out of curiosity... the design of the classes in webware seems to lead
> to prefer a "getter" method property() over self.property approach.
> for example we have request().fields() being a method returning a
> dictionary, instead of having the request().fields dictionary > directly.
> the Page.actions() uses the same idiom. is there a reasoning
> behind this of it's just a matter of taste?
Well, the reasoning is that if you use direct attribute access, you
can't make the value lazy or calculated from another attribute. Of
course, this is no longer the case as of Python 2.2, but it was the
case when that style was developed.
> i'm asking beacuse i'm playing around with that ASP.NET event's thing
> (see the recent thread) and i would like to stick to webware
> conventions as much as possibile. to recap, in hindsight, if you had
> to rewrite th webware class layout today would you guys make the same
Well, I can't speak for Chuck, but I will anyways ;) He's said he'd
use properties if they'd been available. So would I. But to do it now
would mean a large number of changes to the API, even if each change is
very small, and I'm not sure how to reasonably support both interfaces
at the same time (adapters?)