And I do believe that people will replace parsers, as smaller/faster/
better ones come out, in their applications. A major impetus of
Java is to avoid monolithic apps where the user is stuck with the
app exactly as packaged."
Just to play the devil's advocate, are you sure you are not creating a
technical solution to what everyone is more likely to solve with a
non-technical one? If I'm the administrator of my server or my workstat=
ion, and
I see a new SAX driver out there, wouldn't I just read the README befor=
e I even
downloaded it to make sure that its capable of doing what my current do=
es (plus
more maybe?) I doubt very seriously I'd just download new drivers and t=
ry them
until one fails to fail, ya know? And, even if I did, the fact that it =
fails to
fail on the 3 apps I have now, doesn't mean it supports what I want to =
support
on app #4, so I'm going to just read the docs and see what it supports =
most
likely.
Also, once I know what the SAX driver can do, and know that it does wha=
t I
need, why would I want my application playing "20 Questions" every time=
I run
it, when I know what the answer is going to be every time? Why waste th=
e time,
when the kind of situation that you envision might not even happen very=
often?
Have you really checked and seen how likely people are to blindly use n=
ew XML
driver software in such as way as to create the problem you've presente=
d to be
solved?
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
roddey@us.ibm.com
=