Title: Axis Client Performance issue explained

Hi All,

Many thanks to Mike Burati for helping out. A stand-alone application using Axis will perform admirably but a dynamic (mobile) agent such as an applet does poorly due to the fact the Axis Jars are quite big. It is further aggravated if one is using wireless technology and encryption is added on top of that. Delays over 50 seconds for each call object creation or invoke operation can occur. This is because the call can occur while code is being downloaded to the browser. I have arrived at some possible solutions and please let me know if anyone has any thoughts about this.

1. Only use stand-alone clients
2. Use perhaps Sun JAXP (very small jars <20K compared to 3MB> for axis jars)
3. Drop Axis all together (great concept if you can live with stand-alone and non-light clients)

Any Ideas?
Thanks,
Tony

Reply via email to