> > 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
"parser" (ick).
> > > 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
--
David Megginson ak117@freenet.carleton.ca
Microstar Software Ltd. dmeggins@microstar.com
http://home.sprynet.com/sprynet/dmeggins/
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/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe 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)