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.
Depends on how you came to object orientation. I personally
consider most of what goes under that umbrella lately to be
rather alien to its best goals, since the focus is always on some
programming API -- way too concrete.
That is, in the XML world the interface is messages: a protocol
developer's perspective, if you will, and meaning is attributed to
those speech acts. Objects should be an effective paradigm for
attributed those messages into usable/maintainable world views,
but a "Truth" is in each world view, not messages or objects.
I think what seems to be happening with Web Services is the
same thing that happened to CORBA. The original notion was
to start with messages, and make them similar enough that
many tools/APIs/... could reuse them. But instead, it turned into
a way to capture lots of logic in some RPC framework. Which
is a lot less interesting to me, since it's been done so many
times before (and not just in LISP :).