[jdom-interest] Text class in the api
jhunter at acm.org
Tue Oct 23 00:20:34 PDT 2001
I personally am +0 on a Text class, meaning I don't care enough about
the feature to do the work, but I'll advise anyone else who wants to do
philip.nelson at omniresources.com wrote:
> The problem with building the files from html content may also be a good
> excuse to put the Text class to work. A further optimization in SAXBuilder
> would be to keep the last Text node for the current element and append to it
> as successive calls to characters() occur, but still accounting for mixed
> content. This combined with a Text.append(char, int, int method) *should*
> improve performance and memory use in some cases. Element would have an
> addContent(Text) method added.
> There are other ways to do this of course, but I think using a Text class
> has advantages. We might consider implementing the Text internal storage as
> char instead of String or StringBuffer. By doing this, we could get the
> fast(er) append functionality of StringBuffer but near the efficiency of
> String which would still be the most common use case.
> Do we want to go forward with implementing the Text class? I think we
> should make a decision one way or the other on it. I am in favor of it FYI
> and it's now or never for all practical purposes as a 1.0 release shouldn't
> be that far off.
> As before, HELP WANTED!
> To control your jdom-interest membership:
More information about the jdom-interest