XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] Speed in Languages and Browser Architectures



> -----Original Message-----
> From: derek denny-brown [mailto:zuligag@gmail.com]
> Sent: Friday, March 02, 2007 12:40 PM
> To: Elliotte Harold
> Cc: Rick Marshall; Tei; xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Speed in Languages and Browser Architectures
 
> Except that we are talking about the performance of XML parsers, and
> XML is all about string processing and Java string processing is slow.
>  Java XML parsing will never be faster than a good XML parser written
> in C.  There is just too much overhead, and C benefits from 'struct's,
> the lack of which hinders ones ability to write certain constructs
> efficiently in Java.    Any sufficiently fast Java XML parser could be
> ported to C and made faster in the process.

You would know the answer and be able to talk about it, so I'll ask you,
Derek:  Aren't the Microsoft .NET parsers faster than the Native parsers?
If so, is that because the MSXML crew have been so busy with the plumbing
that they haven't been able to focus on optimization, because .NET string
processing is faster than Java, or what?




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


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

Copyright 1993-2007 XML.org. This site is hosted by OASIS