[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Why XML for Messaging?

• To: 'Derek Denny-Brown' <derekdb@m...>, Chiusano Joseph <chiusano_joseph@b...>, xml-dev@l...
• Subject: RE: Why XML for Messaging?
• From: "Bullard, Claude L (Len)" <len.bullard@i...>
• Date: Fri, 3 Jun 2005 08:32:31 -0500

And that means the RFPs are ahead of the market.  Not 
a bad thing necessarily for the folks selling the 
soon-to-be commodities but problematic for the mid 
tier vendors bidding them.  Out of sync.

Again, as you say, put custom formats or the ISO 
formats front and center.  Just as info, keep in 
mind that some of the edge pieces run on batteries. 

Benchmark web services.  This is possibly a good 
paper for someone at a future XML conference: 

"Configuring XML and Web Services for Performance 
in Large Integrated Real Time C3 Systems".

Since that can be competition-sensitive, it might 
not be seen for awhile.

len


From: Derek Denny-Brown [mailto:derekdb@m...]

COTS only applies when the market has entered commodity mode.  XML
messaging has a ways to go before it is a commodity.  The current SOAP
vs REST debate demonstrates that.  If it were a commodity, there would
be no space for such debate.  Buying COTS XML acceleration today is akin
to buying SGML COTS software 5-10 years ago... it exists, but it targets
vertical markets.  When it moves out of the vertical markets into the
mass markets, then it will be commodity.  There are excellent options
available, but don't expect any of them to be around in any recognizable
form in 5 years.

• Prev by Date: RE: Why XML for Messaging?
• Next by Date: JAXB SecurtiyException with NamespaceContext
• Previous by thread: RE: Why XML for Messaging?
• Next by thread: RE: Why XML for Messaging?
• Index(es):
  • Date
  • Thread