You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "??(hjcom)" <Ex...@hitel.net> on 2001/01/30 04:00:20 UTC

using SAX API

As I see the source code of Xalan-C, Xalan-C uses DOM parser
to parse and construct a source tree.
Using DOM parser is so big a burden to the CPU and memory of the system,
since it maintains tree nodes in the heap.
In Cocoon2, they will use(or now use) SAX API for transformation.

So is it possible to use SAX api for transformation in XSLT?

Re: using SAX API

Posted by Dean Roddey <dr...@charmedquark.com>.
I meant Xalan, not Cocoon.

--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
droddey@charmedquark.com
http://www.charmedquark.com

"We're gonna need a bigger boat"


----- Original Message -----
From: "??(hjcom)" <Ex...@hitel.net>
To: <xe...@xml.apache.org>
Sent: Monday, January 29, 2001 8:09 PM
Subject: RE: using SAX API


> I think the facts are not like what you said..
> Surely Cocoon version 1 uses some tree representatoin.
> I think it is the Xalan-Java Document Table Model, which is
> internally used in Xalan-Java.
> But Cocoon version2 uses no tree representation in transformation.
>
> Here's a part of the cocoon 2 document.
>
>
============================================================================
> =========
> For the above reasons, Cocoon 1 was based on the DOM level 1 API
> which is a passive API and was intended mainly for client side operation.
> This is mainly due to the fact that most DOM implementations require
> the document to reside in memory. While this is practical for small
> documents and thus good for the "proof of concept" stage,
> it is now considered a main design constraint for Cocoon scalability.
>
> Since the goal of Cocoon 2 is the ability to process simultaneously
> multiple 100Mb documents in JVM with a few Mbs of heap size,
> careful memory use and tuning of internal components is a key issue.
> To reach this goal, an improved API model was needed.
> This is now identified in the SAX API which is, unlike DOM,
> event based (so active, in the sense that its design is based on
> the inversion of control principle).
>
============================================================================
> ====
>
> Xalan-J supports interfacing with SAX api.
>
> Here's a part of the features of Xalan-J
>
> -Can interface to a SAX document handler or to
> any XML parser that produces Java DOM Trees .
> -Can output to SAX or DOM .
>
> But Xalan-C doesn't provide such kind of functionality.
>
> I want to know that the future version of Xalan-C will have
> some functionality of interfacing with SAX API.
>
>
> -----Original Message-----
> From: Dean Roddey [mailto:droddey@charmedquark.com]
> Sent: Tuesday, January 30, 2001 12:06 PM
> To: xerces-c-dev@xml.apache.org
> Subject: Re: using SAX API
>
>
> My understanding is that they've moved to a proprietary tree
representation
> optimized for their own needs.
>
> --------------------------
> Dean Roddey
> The CIDLib C++ Frameworks
> Charmed Quark Software
> droddey@charmedquark.com
> http://www.charmedquark.com
>
> "We're gonna need a bigger boat"
>
>
> ----- Original Message -----
> From: "??(hjcom)" <Ex...@hitel.net>
> To: <xe...@xml.apache.org>
> Sent: Monday, January 29, 2001 7:00 PM
> Subject: using SAX API
>
>
> > As I see the source code of Xalan-C, Xalan-C uses DOM parser
> > to parse and construct a source tree.
> > Using DOM parser is so big a burden to the CPU and memory of the system,
> > since it maintains tree nodes in the heap.
> > In Cocoon2, they will use(or now use) SAX API for transformation.
> >
> > So is it possible to use SAX api for transformation in XSLT?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>


Sorry...

Posted by "??(hjcom)" <Ex...@hitel.net>.
I thought that this mailing list was xalan-c-dev mailing list.
I misunderstood. It was my mistake... 
I apologize for that...Sorry.


RE: using SAX API

Posted by "??(hjcom)" <Ex...@hitel.net>.
I think the facts are not like what you said..
Surely Cocoon version 1 uses some tree representatoin.
I think it is the Xalan-Java Document Table Model, which is
internally used in Xalan-Java.
But Cocoon version2 uses no tree representation in transformation.

Here's a part of the cocoon 2 document.

============================================================================
=========
For the above reasons, Cocoon 1 was based on the DOM level 1 API
which is a passive API and was intended mainly for client side operation.
This is mainly due to the fact that most DOM implementations require
the document to reside in memory. While this is practical for small
documents and thus good for the "proof of concept" stage,
it is now considered a main design constraint for Cocoon scalability.

Since the goal of Cocoon 2 is the ability to process simultaneously
multiple 100Mb documents in JVM with a few Mbs of heap size,
careful memory use and tuning of internal components is a key issue.
To reach this goal, an improved API model was needed.
This is now identified in the SAX API which is, unlike DOM,
event based (so active, in the sense that its design is based on
the inversion of control principle).
============================================================================
====

Xalan-J supports interfacing with SAX api.

Here's a part of the features of Xalan-J

-Can interface to a SAX document handler or to
any XML parser that produces Java DOM Trees .
-Can output to SAX or DOM .

But Xalan-C doesn't provide such kind of functionality.

I want to know that the future version of Xalan-C will have
some functionality of interfacing with SAX API.


-----Original Message-----
From: Dean Roddey [mailto:droddey@charmedquark.com]
Sent: Tuesday, January 30, 2001 12:06 PM
To: xerces-c-dev@xml.apache.org
Subject: Re: using SAX API


My understanding is that they've moved to a proprietary tree representation
optimized for their own needs.

--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
droddey@charmedquark.com
http://www.charmedquark.com

"We're gonna need a bigger boat"


----- Original Message -----
From: "??(hjcom)" <Ex...@hitel.net>
To: <xe...@xml.apache.org>
Sent: Monday, January 29, 2001 7:00 PM
Subject: using SAX API


> As I see the source code of Xalan-C, Xalan-C uses DOM parser
> to parse and construct a source tree.
> Using DOM parser is so big a burden to the CPU and memory of the system,
> since it maintains tree nodes in the heap.
> In Cocoon2, they will use(or now use) SAX API for transformation.
>
> So is it possible to use SAX api for transformation in XSLT?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org



Re: using SAX API

Posted by Dean Roddey <dr...@charmedquark.com>.
My understanding is that they've moved to a proprietary tree representation
optimized for their own needs.

--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
droddey@charmedquark.com
http://www.charmedquark.com

"We're gonna need a bigger boat"


----- Original Message -----
From: "??(hjcom)" <Ex...@hitel.net>
To: <xe...@xml.apache.org>
Sent: Monday, January 29, 2001 7:00 PM
Subject: using SAX API


> As I see the source code of Xalan-C, Xalan-C uses DOM parser
> to parse and construct a source tree.
> Using DOM parser is so big a burden to the CPU and memory of the system,
> since it maintains tree nodes in the heap.
> In Cocoon2, they will use(or now use) SAX API for transformation.
>
> So is it possible to use SAX api for transformation in XSLT?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>