Dennis Sosnoski wrote:
> Gateways generally can't do much to reduce the actual parser overhead of
> XML processing, though I did implement a binary interface between one
> vendor's gateway and Java applications that gave about a 3x performance
> advantage for a range of XML documents (as opposed to direct parsing of
> XML text, using a JAXP interface in both cases).
>
>
When the service is just getting some data from the database and the
queries are repeated,
there some caching gateway products that will cache results so the
gateway will return the
result from the cache instead of going to through the service. This not
only reduces the data
overhead but XML processing overhead
> I'm not sure what you mean by "when using a StAX parser for fragments of
> a large document". Most WS applications involve processing the entire
> document, and for this case SOAP message exchange is definitely
> considerably slower than RMI.
It's possible to use StAX parsers like Woodstox and XFire to context
route the data which doesn't
require the entire data. Nevertheless, I prefer to "plug in"
intermediaries and pass data through the
API as objects.
H.Ozawa
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
