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] Pushing all the buttons

[ Lists Home | Date Index | Thread Index ]

Simon St.Laurent wrote:

> tbray@textuality.com (Tim Bray) writes:
> 
>>Let me see, they're going to do Web Services with a binary XML format
>>based on ASN.1, which is "a telecommunications standard that is the
>>binary equivalent of XML Schema"; Sun Distinguished Engineer
>>Pelegri-Llopart said "The main point here is there is almost an order
>>of magnitude between straightforward Web services using XML encoding
>>and an implementation that takes care of binary encoding."  They're
>>also going to have a "Fast Infoset" and "Fast Schema".
> 
> 
> It makes sense to me, given the low-to-negative value that most
> developers of projects in that space give to XML as anything beyond
> "something which has lots of toolkits".  


Fwiw, time invested in XML parsing would pay dividends. 
Crimson/Xerces ain't nothing to write home about and they seem to 
have the lions share of deployments in Java-land.


"The main point here is there is almost an order of magnitude 
between straightforward Web services using XML encoding and an 
implementation that takes care of binary encoding," - Eduardo.

Find a customer and imagine which you think they want to hear- "yes 
its slower but it'll be up in 12 weeks, cheap and cheerful, and 
anybody in oppers can read what's coming in off the wire", or "yes 
it blazes but it'll take six months cost more, and no, oppers won't 
be able to understand anything". Yes I do draw a direct correlation 
with text wire formats over internet protocols with cost-effective 
high relevancy integrations shipped earlier. Call me biased, but I 
honestly don't know how anything got done at all in middleware 
before XML and HTTP came along.

If there are plenty of customers who are deeply concerned about 
performance then maybe this work has value, but I still think 
optimizing the parsers is a better strategy, and even if you proved 
it wasn't,  I think I'd look for a briefer text format first 
(xml2rnc for example), before I'd get into binary codecs.

Just as long as they don't start proposing fast HTTP or fast TCP :)

Bill de hÓra





 

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

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