[
Lists Home |
Date Index |
Thread Index
]
- From: David Megginson <david@megginson.com>
- To: xml-dev@ic.ac.uk
- Date: Mon, 10 May 1999 13:18:06 -0400 (EDT)
roddey@us.ibm.com writes:
> See my other response on the related thread. We have chosen what we
> consider the correct level of granularity for thread safety, which
> is at the per-parser level. I'm discussing the 2.x versions here,
> Java and C++ are the same in this respect. We see little use in
> having multiple threads in a single parser. It is more appropriate
> to have a parser per-thread.
The point here, I suspect, is not that it is not a good idea to have
multiple threads inside the same parser, but that it is not a good
idea to use the same parser in multiple threads outside of it.
I can imagine a parser some day running several internal threads on a
multiprocessor machine -- one, perhaps, for I/O, one for tokenisation,
one for structure recognition, and one for schema-based validation. I
don't know if I'd bother doing this right now, since single-threaded
parsers are so fast anyway, but who knows what tomorrows technology
and business requirements will be?
All the best,
David
--
David Megginson david@megginson.com
http://www.megginson.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 (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)
|