You will have to create your own InputSource unless the source matches one of the provided sources. Subclass the InputSource (sax/InputSource.hpp).
Regards,
Thom Bentley
Iris Associates, 5 Technology Park Drive, Westford, MA 01886
Using your lights makes you bright. It's smart to use your headlights at dawn and dusk.
"Williamson, Siehnai" <[EMAIL PROTECTED]> wrote on 06/22/2001 02:01:15 PM:
> I need to clarify. I'm actually being fed the xml data through a
> buffer from another application. My application does not know the
> file's path. As a result, I don't think I can use LocalFileInputSource.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, June 22, 2001 12:36 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Separate MemBufInputSource as input
>
> Also, since you are reading from a file, should you not be using the
> LocalFileInputSource class instead .. that should hopefully take care of
> very large xml files ...
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, June 22, 2001 10:23 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Separate MemBufInputSource as input
> >
> >
> >
> > I don't think there is. You'll probably have to use one
> > MemBufInputSource
> > and multiplex it yourself.
> >
> > Dave
> >
> >
> >
> >
> >
> > "Williamson,
> >
> > Siehnai" To:
> > "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> > <swilliamson@doc cc: (bcc:
> > David N Bertoni/CAM/Lotus)
> > ucorp.com> Subject:
> > Separate MemBufInputSource as input
> >
> >
> > 06/22/2001 01:19
> >
> > PM
> >
> > Please respond
> >
> > to xerces-c-dev
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> >
> > I am using the MemBufInputSource as my input source for the
> > SAX parser.
> > However, my application will have to stream the data
> > piecemeal as separate
> > MemBufInputSource's to the SAX parser because of the size of the input
> > files.
> >
> >
> > For instance, a MemBufInputSource will represent only a chunk of the
> > actual xml file. When the SAX parser reaches the end of that memory
> > buffer, it will need to wait for the next MemBufInputSource
> > to continue
> > parsing rather than ending the parse or giving an error. Is
> > there a way
> > for the SAX parser to parse one buffer, wait, then parse
> > another buffer,
> > wait, and so on, until you tell the parser that this is the
> > last buffer?
> >
> >
> >
> >
> >
> > Siehnai Williamson
> > DocuCorp International, Inc.
> >
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
- Separate MemBufInputSource as input Williamson, Siehnai
- Re: Separate MemBufInputSource as input Miroslaw Dobrzanski-Neumann
- Re: Separate MemBufInputSource as input David_N_Bertoni
- RE: Separate MemBufInputSource as input jeetu . gulati
- RE: Separate MemBufInputSource as input Michael Nigbor
- RE: Separate MemBufInputSource as input Williamson, Siehnai
- RE: Separate MemBufInputSource as input Williamson, Siehnai
- RE: Separate MemBufInputSource as input Vinodkumar S
- tbentley
