[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal

• From: David Megginson <ak117@f...>
• To: Tim Bray <tbray@t...>
• Date: Sun, 14 Dec 1997 06:35:18 -0500

Tim Bray writes:
 > At 09:01 PM 13/12/97 -0500, David Megginson wrote:
 > >I have worried about this myself.  My design goal with Ælfred has been
 > >to limit myself to two class files: one for the parser itself, and one
 > >for the interface for the callbacks -- hence the separate event for
 > >attributes.  This decision has forced some pretty severely hacked-up
 > >internal code accompanied by very careful documentation.
 > 
 > Hmm, isn't this what JAR and so on are for?  Seems like an awfully 
 > severe design constraint.  I certainly agree with "small" as a design
 > goal, but it seems like limiting class file count carries a pretty
 > high price. - Tim

It is a painfully high price, especially in terms of coding
difficulty; if NS 3.*, NS 4.*, MSIE 3.*, MSIE 4.*, and HotJava all
accepted the JAR files (or any other archive format), then I wouldn't
worry.  As it stands, however, that is not the case, and it is
essential that Ælfred be easy to use in existing browsers as well as
future ones.  That is the same reason that I didn't use any JDK 1.1
features, despite the fact that I _like_ JDK 1.1.

I am willing to be convinced that an extra couple of class files won't
make a difference to Java applet writers (with no special interest in
XML), but I will need to hear that from them.


All the best,


David

-- 
David Megginson                 ak117@f...
Microstar Software Ltd.         dmeggins@m...
      http://home.sprynet.com/sprynet/dmeggins/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal
    • From: Peter Murray-Rust <peter@u...>

• References:
  • Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal
    • From: Tim Bray <tbray@t...>

• Prev by Date: XML-DEV list errors on weekends
• Next by Date: Corrected Examples: XML Architectural Forms
• Previous by thread: Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal
• Next by thread: Re: YAXPAPI (Yet Another XML Parser API)- an XDEV proposal
• Index(es):
  • Date
  • Thread