RFC: Simple XML Event-Based API for Java
ak117 at freenet.carleton.ca
Wed Dec 17 14:51:42 GMT 1997
Paul Prescod writes:
> > The advantage is that the same XmlApplication object can work with
> > more than one XmlProcessor at the same time (though it is not required
> > to be able to do so).
> If you use the name "Application" then it makes sense to require a
> single application to support multiple processors. Jade is an example of
> an application that supports multiple processors. If we use the word
> ***Consumer, then it makes sense that there should be a single consumer
> per Producer.
I'm using the XML terminology, where "processor" actually means
> > > This could be done by having the app ask the processor for the location
> > > of the last event in some non-standardized way, but that's kind of
> > > kludgy. On the other hand, maybe this is just too fancy for a
> > > "simple" API.
> > I think that it probably is too fancy.
> Maybe, but it also seems very important. A processor that can't tell you
> where your errors are is very frustrating. Perhaps there should
> immediately be a "level 2" that supports this.
These are two separate things. Adding a "col" argument to the error()
callback is not so tricky, but providing the exactly location of every
start and end tag or data chunk is too complicated.
All the best,
David Megginson ak117 at freenet.carleton.ca
Microstar Software Ltd. dmeggins at microstar.com
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;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev