OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] XML as generic villain

[ Lists Home | Date Index | Thread Index ]

--- Rex Brooks <rexb@starbourne.com> wrote:


As poorly written and misinformed as the article
surely is, I find the analogy of video cards
intriguing: text-oriented video systems were
overwhelmed by the demands of GUIs and graphics, and
the vendors threw hardware at the problem to make it
go away.  Current networks are oriented toward
protocols whose "visible" information is confined to
well-defined header fields, but XML makes the entire
content of the message potentially visible to routers,
caches, firewalls, etc. Not only that, the fact that
many XML applications (at least those created by
default in VS.NET, etc.) "tunnel" the Net protocols
creates a *need* for such intermediaries to understand
the XML content of an entire message in order to do
their job.  

Assuming that the RESTifarians don't persuade the
world to just Not Go There, I can very easily imagine
network admins being overwhelmed by XML in the very
near future, much like 1985 video cards were
overwhelmed by GUIs.  Why *not* offload as much of the
grunt work of XML network processing to specialized

That's not to say that I believe that the current
state of the world requires this or that the current
products provide adequate solutions, only that I don't
believe the situation is laughable.


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS