Lists Home |
Date Index |
That's interesting. Why do you think this is the case?
A: I'm not sure so far. Relational DBs are easy to
build, the tools are there, the skills are there,
and I don't see XML as a compelling alternative to a
database or XPath for SQL and XQuery looks like
SQL. So, right now, I don't have a compelling
case to move away from hybrid architectures that
use back end relational systems and front end
markup clients. I can see it on the client side
I'd definitely rather use XSLT when it is time to
transform, but much depends on the source. I like XML DOM for a
document model, that is, for manipulation of the data behind the display.
B: Business rules in XML? An XML Schema plus Schematron
can do a lot, but not enough. I still need procedural business
objects, transaction managers, etc.
The relational db probably still will take the processing load
a lot better than a pure XML DB system regardless of who
is driving and possibly be a much easier development for
the medium skilled developer. I don't think we are nearly
in a position experience wise to say otherwise, but I'm
open to arguments to the contrary. The issue is that the
improvements have to be extraordinary, not just a small
From: Naren Chawla [mailto:firstname.lastname@example.org]
In my mind, performance is one aspect. What is much more interesting is -
A. Is it possible to cut development cost for web applications using XML,
XML Schema, XSLT, XPath, XQuery drastically ?
B. Is it easy to make changes to this XML-based web applications to
accommodate business changes ? In other words, are this applications easier
to maintain ?
More I work with XML technologies, I am convinced that the current JSP/ASP
way of building web applications has outlived its life-cycle.