Because, in that analogy, the passengers aren't paying for a engine room
tour. They're paying for the cruise experience, not the behind the scene
infrastructure necessary to make it happen. Arguably the same thing goes
for many, if not all, situations where a 'user' might interact with a system
that utilizes XML behind the scenes. The users aren't paying for the the
thrill of seeing XML parsing in action, they're expecting an application of
some sort to do it's job.
That said, just because a system is 'designed' to operate without users
seeing the raw data, it doesn't mean the system shouldn't be programmed to
ward off problems users interaction might cause. Assume the data could
suffer all manner user-inflicted problems. Never assume otherwise. For at
some point someone will decide it's worth mucking around with the data.
-Bill Kearney
-----Original Message-----
> From: Simon St.Laurent Why bury the good stuff in the engine room? Or at
> least, why lock tourists out of the engine room?
