[
Lists Home |
Date Index |
Thread Index
]
- From: "Don Park" <donpark@docuverse.com>
- To: <xml-dev@ic.ac.uk>
- Date: Thu, 2 Dec 1999 22:14:12 -0800
>The advantage of SAX ( and attributes in XML)
>is that we have attributes in place when startElement
>is invoked. We know what are some properties of this
>element right when element begins.
While there are indeed practical benefits to having
attributes readily available, event-based APIs like
SAX unintentionally encourage novice XML programmers,
who are not fully aware of attribute-vs-element issues,
toward designing data formats that favoring attributes
over child elements.
>At that point could we get the information about
>the another properties this element has
>( the child elements ) ?
At the expense of requiring multithread support,
most of this problem goes away if the parser runs
in a separate thread so that by the time the attribute
stored as a child element is requested, it is already
available. If not, the requester's thread simply blocks
until it is.
Best,
Don Park - mailto:donpark@docuverse.com
Docuverse - http://www.docuverse.com
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|
