Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Message-ID: <3A775B4B.EA4DD125@cs.indiana.edu>
Date: Tue, 30 Jan 2001 19:24:43 -0500
From: Aleksander Slominski <aslom@cs.indiana.edu>
MIME-Version: 1.0
To: axis-dev@xml.apache.org
Subject: Re: [AXIS ARCH] - Message Internals
References: <OFEE4E1045.594CB014-ON852569E4.004EECC3@raleigh.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Sam Ruby wrote:

> There are two basic approaches to streaming: a PUSH model, which SAX
> represents.  Or a PULL model, which some of the APIs which have been
> submitted to ECMA for standardization represent.  Between these two
> alternatives, James seems to favor a pull model.  I'm inclined to agree.

Hi,

there are actually more alternatives for PULL model. In our SoapRMI
implementation we are using very simple XML pull parser that is so far
very well working in our C++ and Java version of SoapRMI library.

Xml Pull Parser (XPP) provides a very simple, high performance 
pull model to parse Reader or String input. It  was designed for 
and it should be optimal for applications that require
very small size XML parser - the jar file with compiled classes
is around 20 KB. Its simple pull parsing API (identical for Java and C++)
is especially well suited for unmarshalling complex data structures
from XML (such as in SOAP).

For documentation and source code under open source license
please see http://www.extreme.indiana.edu/soap/

Thanks,

Aleksander Slominski
soaprmi@extreme.indiana.edu
Extreme! Computing Lab
--
Aleksander Slominski, IU, http://www.extreme.indiana.edu/~aslom
As I look afar I see neither cherry Nor tinted leaves Just a modest hut
on the coast In the dusk of Autumn nightfall-Fujiwara no Teika (1162-1241)