> The Sun RI also uses a custom pull-parser, which is pretty > much the fastest parsing technology you can build. We chose > to go with standard JAXP (SAX) APIs to allow > developer-friendliness and the ability to use whatever parser > you already have kicking around, though we may revisit this > in the future as well (esp if a standard pull parser API is > developed as a JSR).
There is a JSR for this: http://jcp.org/jsr/detail/173.jsp. Because of much better performance, some SOAP implementations have used pull parser, including Sun. When I was talking to someone from SUN about this point, I don't think she felt comfortable about using a non-standard parser either ... Though SAX is standard, I cannot say that SAX api is friendly for developers. Otherwise, why does axis need to have SAX events recorded for replay ... I have tried some perf measurement of both jax-rpc ri and axis. In performance, the RI is better but NOT significant. I don't think it's very difficut to achieve same or better perf without changing paring mechanism. My feeling is that current Axis is much more mature than the RI I was trying. HP does use Axis in client side and toolkit. Regarding the perf, we also implement some http1.1 features that I already posted the souce codes, we modified, to the Axis-dev list. The perf improvement is around 10% ~ 15%. We will try to have as more contribution to Axis as we can and as you need :) but I am not representing HP ... -chen
