Thanks Ashanka. Must a client support HTTP/1.1 chunking in order to use synapse? Best, Garth
On Mon, May 5, 2008 at 10:13 AM, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > Garth > > > > 2df > > <ns:getQuoteResponse xmlns:ns="http://services.samples/xsd";><ns:return > > > type="samples.services.GetQuoteResponse"><ns:change>-2.8645613863894557</ns:change><ns > > > :earnings>12.30521720248757</ns:earnings><ns:high>-151.78678259858341</ns:high><ns:last>154.53038305767686</ns:last><ns:lastTradeTimestamp>Sat > > May 03 18:55:1 > > 7 PDT > 2008</ns:lastTradeTimestamp><ns:low>160.3361975912104</ns:low><ns:marketCap>-358967.49623407796</ns:marketCap><ns:name>IBM > > Company</ns:name><ns:open>15 > > > 9.5352172771564</ns:open><ns:peRatio>25.471190753873586</ns:peRatio><ns:percentageChange>-1.7026538696082525</ns:percentageChange><ns:prevClose>168.240970024 > > > 54968</ns:prevClose><ns:symbol>IBM</ns:symbol><ns:volume>5145</ns:volume></ns:return></ns:getQuoteResponse> > > 0 > > > > > > ============== > > > > Note the "2df" before the response xml and the "0" after. Is anyone > > seeing the same thing? Any ideas where that is from? I've attached a > > JMeter test that I used to call the service. Note that the "View > > Results Tree" listener cannot render the xml after executing the test. > > > > > The "2df" and "0" are the sizes of the "chunks" sent, as this is using HTTP > chunking (available with HTTP 1.1) to perform better streaming. If you do > not "chunk", an HTTP message must write its size as the "Content-Length" > header, which basically requires you to buffer the message into memory to > find out how many bytes it will spread to > > Chunking is harmless, and good in performance, and will not have *any* bad > effect on anything else whatsoever AFAIK > > asankha >
