[gui-dev] Xerces4J or JAXP?

I've seen many articles stating that now the bundled version of JAXP in
J2SE 1.4 or 1.5 is faster and less resource intensive than the separate
Xerces4J implementation (because Sun has integrated tightly large parts
of Xerces within Java 1.4 to implemente JAXP, and optimized it so that
it can use undocumented but faster internal interfaces, that are also
used now by so many other J2EE components, notably SOAP for web
services).

Wouldn't it be true for J2SE-based Limewire too, or are those reports
only true for J2EE applications on application servers? Do we still
need to use a separate Xerces4J JAR on Windows? Or on OSX? Do we use
something that is specific to Xerces and not part of the JAXP
interface?

That's a good question since we have stopped the developments for
MacOS9: have we switched to Java 2 with version 1.3.1 minimum (as
bundled in past versions of LimeWire) or to Java 1.4 minimum (Java 5.0
is now officially released by Sun on Windows and Linux, and will be
soon on OSX too...)

Or do we plan to continue with Xerces4J, bundling when needed a newer
(smaller) version now optimized to work with Java 1.4 or 5.0 integrated
fast JAXP support?

-- Philippe.



	

	
		
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
_______________________________________________
gui-dev mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/gui-dev