[
Lists Home |
Date Index |
Thread Index
]
From: "Rich Salz" <rsalz@datapower.com>
> >For the case of internal entities, the text can still be all in a single buffer
> >in my suggestion shows. I was trying to point out that the claims that
> >supporting (internal) entity references for documents that normally won't
> >have entity references *must* cause significant increase in space or
> >performance seem to fail to take into account some implementation
> >techniques.
>
> I must have missed it. Either you inline expand and get all the text
> in one buffer, you you do SAX style multiple calls or force the app
> to do the multiple calls by putting in a marker.
Or you expand inline what can be expanded inline and flag whether there
are any entities that could not be expanded and are still delimited
(e.g. with the object replacement character), and select the function
to run based on that flag. You have your cake and eat it.
The argument in the thread is whether supporting entities but not using
them must cause show-stopping space or time degradation compared to
not supporting entities, as was claimed. (And, more than that, the
claim that supporting internal entities requires multiple buffers.)
Cheers
Rick Jelliffe
|
