I second that... And would just add that you might want to think about when your application is just too 'chatty' for SOAP...
-pc On Tue, 16 Nov 2004 08:48:30 -0900, Elaine Nance <[EMAIL PROTECTED]> wrote: > 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 -- > <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > >
