Sandy Gao wrote:
There seem to be 2 ways to pass features/properties to components: via
reset() method and via setFeature/Property() methods. Currently most Xerces
components rely on reset() to get feature/property values, which is the
reason why reset is so slow.
The reset() and setFeature/Property() methods perform
different roles for the component. I don't see how the
latter can take the place of the former.
This alternative suggests that, for those components who care about
performance, they *could* ignore feature/property values when reset() is
called, and only pay attention to setFeature/Property() for the value
changes. (They will be slower than reset(), but the assumption here is that
people don't change feature/property values very often, so they won't be
called very often.)
But the only time that setFeature/Property() is called
is when settings change after calling parse(). So it's
not like the parser configuration can call the compo-
nent's setters for the features/properties that it
cares about (and then only when it's the first time or
when the setting has changed).
In general, I agree that this is one area that can be
analyzed for performance but I don't see how we're
going to make it work correctly with the proposed
changes.
--
Andy Clark * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
