SOAP is not designed to create compact dataflows. It is designed for interoperability and, because it is XML, extensibility. IMHO, I would *not* use SOAP for purely internal processes if speed or stream size matters (where faster/smaller) is better.

In that case I would go strictly with a socket-level approach.

Just my 2 small coins,
Elaine

Vy Ho wrote:

I look at a message send back from the server to a client in Axis, and was very surprised that most of the text is not the data that I need to send, but declaration and long namspaces. Is it possible to reduce these down and still comply with Soap?


Thanks,

vh


<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Computers are useless. They can only give you answers. | -- Pablo Picasso -- <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




begin:vcard
fn:Elaine Nance
n:Nance;Elaine
org:State of Alaska;Commerce, Community and Economic Development
adr:;;PO Box 110800;Juneau;AK;99811-0800;USA
email;internet:[EMAIL PROTECTED]
title:Analyst Programmer IV
tel;work:907.465.2109
tel;fax:907.465.2858
x-mozilla-html:FALSE
url:http://www.commerce.state.ak.us
version:2.1
end:vcard

Reply via email to