Lists Home |
Date Index |
- From: Lars Marius Garshol <firstname.lastname@example.org>
- To: "XML Developers' List" <email@example.com>
- Date: 25 Mar 1999 19:29:49 +0100
* Ronald Bourret
| What is the possible benefit of making any property write-only?
| That is, can any harm ever come from reading a property?
* David Megginson
| There are three benefits:
| 1. Keep the API absolutely as small as possible.
| 2. Avoid confusion.
| 3. Allow properties to be unknown until set.
These are all real benefits, but the disadvantage is rather large I'm
afraid: it makes assembling a processing solution from reusable
components much more difficult, since one component can't learn how
the others have modified the parser settings.
I think we should make all properties readable, which means we split
them into read-write/read-only properties. This should maintain
benefits 1 and 2 even better than the write-only/read-only split,
since most people probably expect read-write/read-only properties like
e.g CORBA attributes.
I also think we should go even further and make all features readable,
so that a filter can see if a feature has been enabled or not. Without
knowing the exact set of features I think disabling reading is
potentially very limiting.
| Any attempt to access a property can generate a
| SAXNotSupportedException (or the derived SAXNotRecognizedException),
| but there is no guarantee that they will be symmetrical.
Maybe we should have a SAXInvalidValueException too, so that the
parser/filters can reject invalid values without risking
misinterpretation on the part of applications/filters?
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)