Since you could just effectively rip off the existing one, probably so.
--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
[EMAIL PROTECTED]
http://www.charmedquark.com
"Why put off until tomorrow what you can
put off until the day after tomorrow?"
----- Original Message -----
From: "anand awasthi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 04, 2001 11:49 AM
Subject: Re: wrapping the Xerces parser !!
> thanks a lot for suggesting better options...
>
> i guess i forgot to mention the time frame,
> i got only a week to do this.
> is 1 week sufficient enough time for coding on DOM
> Parser front ??
>
> thanks
>
>
>
>
> yeah
> --- Dean Roddey <[EMAIL PROTECTED]> wrote:
> > You might want to just consider writing your own
> > DOMParsre and SAXParser. If
> > you look inside them, they aren't very complicated.
> > And doing so will let
> > you provide your own interfaces without paying the
> > extra performance cost of
> > going through a middel parser layer. You'd just wire
> > the scanner directly to
> > your interface, just like DOM/SAXParser does.
> >
> > --------------------------
> > Dean Roddey
> > The CIDLib C++ Frameworks
> > Charmed Quark Software
> > [EMAIL PROTECTED]
> > http://www.charmedquark.com
> >
> > "Why put off until tomorrow what you can
> > put off until the day after tomorrow?"
> >
> > ----- Original Message -----
> > From: "anand awasthi" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, June 04, 2001 11:25 AM
> > Subject: wrapping the Xerces parser !!
> >
> >
> > > Hi,.
> > >
> > > I am making an XML ADATPER which will parser
> > incoming
> > > client XML file/generate DOM and convert DOM to
> > XMLs
> > > ans send them to clients.
> > >
> > > I am using Xerces parser, but i dont want my
> > client to
> > >
> > > interact with Xerces implementation directly. so i
> > > want to wrap the Xerces implementation within my
> > api.
> > > To do this, i am planning to extend the Xerces
> > DOM/SAX
> > > APIs and then ask the clients to use my own APIs
> > > inplace of Xerces,
> > >
> > > e.g.
> > >
> > > XML_DOM_Document : DOM_Document
> > > ( where XML_DOM_Document is my class and
> > DOM_Document
> > > is Xerces impelmentation).
> > >
> > > later my clients will call methods on
> > XML_DOM_Document
> > > instance.
> > >
> > > e.g.
> > >
> > > XML_DOM_Document xmldoc ;
> > > xmldoc.getDocumentType();
> > >
> > > is this inheritance approach good or do you
> > suggest
> > > any better mechanism to wrap Xerces implementation
> > in
> > > some other way ??
> > >
> > > pls enlighten me
> > > thanks
> > > Oni
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Get personalized email addresses from Yahoo! Mail
> > - only $35
> > > a year! http://personal.mail.yahoo.com/
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > 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]
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail - only $35
> a year! http://personal.mail.yahoo.com/
>
> ---------------------------------------------------------------------
> 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]
