[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Partyin' like it's 1999
Guillaume Lebleu wrote: > But once in production, why not switch my Serializer to serialize to YAML, > XML > Binary or what have you (even keep DOM objects for ex. for in-process > communications), as long as both service consumers and producers > agree? I could keep my application that receives DOM objects or SAX events > but have actually something sent on the network that looks totally different > from XML. Because then when something does wrong (and it always does) it's no longer easily inspectable. > I know this would greatly help performance. I know no such thing. Actual measurements are required to make claims about performance. Furthermore, measurements of one specific scenario can not be blindly extrapolated to different scenarios. Optimizations made for one purpose often hinder performance in other scenarios. XML seems to be a fairly good middle-of-the-road approach for a lot (not all) applications. There are applications where XML doesn't fit well. You'll find quite a few of them in http://www.w3.org/TR/2004/WD-xbc-use-cases-20040728/ Perhaps rather than breaking XML for all the cases where it does work well now, we should invent a new format that matches these different needs. One solution does not fit all problems. -- Elliotte Rusty Harold elharo@m... XML in a Nutshell 3rd Edition Just Published! http://www.cafeconleche.org/books/xian3/ http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|