In Xerces the split is most likely to happen because it ran into a child
element or a character or entity reference. It stops, send the data before
the reference, then processes the reference and sends that data, then picks
up again on the other side. This allows applications to know what data
belonged to what entities.
--------------------------
Dean Roddey
The Charmed Quark Controller
Charmed Quark Software
[EMAIL PROTECTED]
http://www.charmedquark.com
"If it don't have a control port, don't buy it!"
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 17, 2001 9:43 AM
Subject: Re: splits in character data.
>
> >I know that character data can be split over subsequent calls to
> >characters(). I was wondering what governs where the splits come.
>
> "Implementation dependent." Typically, splits occur whenever the parser
> runs out of buffer space or changes buffers. Since the size and
arrangement
> of the buffers is entirely up to the individual parser, and buffer usage
> depends on what data is already in that buffer, the simple answer is that
> you don't know, can't know, and have to assume the split can happen at any
> time.
>
> >Can other data be split? For example could
> >attributes be split over multiple calls to startElement.
> Not as SAX is currently defined, no.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
