Anne, Some of the commercial SOAP toolkits have optimization where complete or part of the SOAP message (like header) is stripped off to make the size of the payload small. This kind of optimization is good, when both the Web Service Provider and the Consumer use the same SOAP toolkit because stripping off a part of the SOAP messages will make it a invalid SOAP message.
Maybe we will see such optimization in Axis. Cheers, Praveen --- Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > This is a function of XML. You just have to deal > with it. Your message > must include the full namespace URIs in the > namespace declarations -- > they are in fact defining aliases. These namespace > declarations (e.g., > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope";) > permit you > to specify "soapenv" rather than > "http://schemas.xmlsoap.org/soap/envelope/"; later in > the message. > > There is no way to avoid it. > > If these few extra bytes are a real problem for you, > then you should > try using a binary protocol rather than an XML > protocol. But I can't > think why this would be a real problem for you. Even > a tiny device > shouldn't have an issue with the extra bytes > (working on the > assumption that the device supports XML). Network > bandwidth is now > vitually free. > > Anne > > On 6/16/05, Amihai Fuks <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I've recently started to use SOAP and as I can see > the XML response has > > a huge overhead. All I can see there are long tags > that approximately > > make the response 100 times longer. Can I reduce > tags like: > > > > <soapenv:Envelope > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > There must be a sort of way to alias these long > tags. > > > > Amihai > > > ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com
