Lists Home |
Date Index |
> > The separation of content from presentation (or processing) in XML seems
> > to work okay with similar notions in relational databases, but goes
> > against much of the grain of object-oriented development.
> I don't know. MVC is a common pattern, and I think XML+XSL represents the M+V
> parts very well.
I agree. I'm doing some investigation into various presentation technologies,
and have concluded that the best way to architect a web interface is as an
Model-View-Controller architecture, with the view implemented using XSLT.
It gives the strongest separation between the developer and page builder
roles. (Of course if the same people are fulfilling both roles, then the
distinction does become somewhat blurred).
Martin Fowler is producing an extremely interesting and useful summary of
architectural patterns here: http://www.martinfowler.com/isa/
Transform View is particularly relevant:
To address Simon's wider point, I'm not certain whether the core issue is
that OO and XML are necessarily poles apart, I think it's more that few
people have experience in building the types of loosely coupled systems
that XML facilitates.