SAX: towards a solution

[Tyler Baker]

David Megginson wrote:

> James Clark writes:
>
>  > I don't think using java.util.Dictionary is a good idea:
>  >
>  > 1. JDK 1.2 provides a new Map interface which replaces Dictionary.
>  >
>  > 2. java.util.Dictionary is an abstract base class not an interface.
>  >
>  > 3. java.util.dictionary is weakly typed: it doesn't enforce the
>  > requirement that keys be strings, and it requires values to be cast to
>  > strings.
>  >
>  > I think it would be much better to have an Attributes interface and also
>  > a convenience adapter class that provides a Dictionary implementation in
>  > terms of that interface.
>
> I would like to avoid java.util.Map to keep SAX applet-friendly (it
> will be years before most browsers deployed support even 1.1).  I
> agree that Dictionary is far less than ideal -- what do you imagine
> the attributes interface looking like?

I think JDK 1.2 support will be much sooner than for JDK 1.1 and should not
matter at all for applications anyways.  As, for Java Applets, SUN's Java
Activator should take of that problem.  It is not totally out yet, but the
technical challenges of implementing something like this are minimal and I am
surprised they did not do this a while ago.  Using the new Collections classes in
JDK 1.2 would be a much better idea IMHO.

Tyler


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