On Wednesday 29 September 1999, at 12 h 0, the keyboard of "Ean R . Schuessler" <[EMAIL PROTECTED]> wrote:
> a common library by organization. Let's say that you are writing an XML > program and are using classes from several different organizations. Having > to deal with classes coming out of: com.ibm.xml.xena.*, com.jclark.xml.sax.*, > etc., etc., etc. gets a little confusing. The main strength of the current approach is that it allows two different implementations of SAX to live together, letting the user chose. Doing otherwise would mean having a form of arbitration, to decide which one will be lgpl.xml.sax and which one will be... dropped?
