Hi Rishi,

I have no idea what you mean by "every page coming in."

Xerces is an XML parser.  It parses and optionally validates XML documents.
If you want to build a smaller Xerces binary, then you might post a
question on the Xerces-C list, or search the archive to see if anyone else
has asked the question.

Dave



|---------+--------------------------->
|         |           Rishi Sampat    |
|         |           <[EMAIL PROTECTED]|
|         |           hoo.com>        |
|         |                           |
|         |           02/21/2003 04:04|
|         |           PM              |
|         |           Please respond  |
|         |           to xalan-dev    |
|---------+--------------------------->
  
>--------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                    
                                            |
  |        To:      [EMAIL PROTECTED]                                                  
                                     |
  |        cc:      (bcc: David N Bertoni/Cambridge/IBM)                               
                                            |
  |        Subject: Re: Socket/kernel interaction                                      
                                            |
  
>--------------------------------------------------------------------------------------------------------------------------------|



Hi David,
   Is this DTD and schema validation done for every
page that comes in?
   I was thinking if this a non-recurrent operation
this could be put in a separate library to reasonably
tweak the final binary size.
Thanks!
Rishi

--- David N Bertoni/Cambridge/IBM
<[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi Rishi,
>
> Why do you think Xerces is "a parser which builds
> the parse tree based on
> input from the stylesheet?"  It's a full-featured
> XML parser that supports
> DTD and schema validation, whcih is not a small
> piece of code.  You may
> want to run strip on the shared library, which will
> reduce the size a fair
> amount.
>
> The documentation as you see it is what there is.
> There is not much other
> than documentation of the API.  You can study the
> sample applications for
> more information.
>
> Dave
>
>
>
>
>
>
>                       Rishi Sampat
>
>
>                       <[EMAIL PROTECTED]         To:
>    [EMAIL PROTECTED]
>
>                       hoo.com>                 cc:
>    (bcc: David N Bertoni/Cambridge/IBM)
>
>
> Subject: Re: Socket/kernel interaction
>
>                       02/20/2003 04:59
>
>
>                       PM
>
>
>                       Please respond
>
>
>                       to xalan-dev
>
>
>
>
>
>
>
>
> Hi David,
>     So I guess you are suggesting that Xalan
> interacts
> with Xerces via library API calls...
>
> After building Xerces2.1, I noticed the binary size
> to
> be 3GB, more specifically 3112517 bytes. Wonder why
> is
> the size so huge for a parser which just builds the
> parse tree based on input from the stylesheet?
> Any optimization you suggest? I shall mail this
> question on the Xerces list as well.
>
>
> I have to following as a reference to documentation.
> http://xml.apache.org/xalan-c/apidocs/classes.html
> http://xml.apache.org/xerces-c/apiDocs/index.html
>
> Any suggestions on how to go about these? Is there
> some sort of verbal documentation describing the
> motivation behind the current design to a newbee?
>
> Thanks for the lead about classes that implement
> http
> access for URLs. I shall take a look at those.
>
> Thanks,
> Rishi
>
> --- David N Bertoni/Cambridge/IBM
> <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > Hi Rishi,
> >
> > There is no IPC between Xerces and Xalan.
> >
> > Xerces has some classes that implement http access
> > for URLs.  Take a look
> > at the documentation for more information.  You
> > could also post any
> > questions you have on the Xerces-C list.
> >
> > Stating that XML "runs over TCP/IP" is misleading.
> > XML documents can
> > transferred through a TCP/IP socket, but that's
> just
> > one of many potential
> > communication channels.
> >
> > Dave
> >
> >
> >
> >
> >
> >
> >                       Rishi Sampat
> >
> >
> >                       <[EMAIL PROTECTED]         To:
> >    [EMAIL PROTECTED]
> >
> >                       hoo.com>                 cc:
> >    (bcc: David N Bertoni/Cambridge/IBM)
> >
> >
> > Subject: Socket/kernel interaction
> >
> >                       02/20/2003 01:51
> >
> >
> >                       PM
> >
> >
> >                       Please respond
> >
> >
> >                       to xalan-dev
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> >   I was wondering which are the classes that deal
> > with
> > IPC between Xalan and Xerces. Is IPC in form of
> > sockets?
> >
> > XML runs over TCP/IP. Which are the classes that
> > deal
> > with the kernel and TCP/IP stack? I am assuming
> that
> > only Xerces is involved in communication with the
> > kernel.
> >
> > Thanks,
> > Rishi
> >
> >
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Tax Center - forms, calculators, tips, more
> > http://taxes.yahoo.com/
> >
> >
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - forms, calculators, tips, more
> http://taxes.yahoo.com/
>
>


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/


Reply via email to