>> I initially used SendStream to send my xml back to
>> the client, but I have now switched to using AnswerString.
Using 1.3 MB long string is always slow.
Why don't you use AnswerStream (not SendStream) since your XML seems already
loaded into a stream ? AnswerStream will correctly build the HTTP reply's
header. SendStream is made to give you full control on the reply and of
course you need to build the HTTP header yourself. AnswerStream is one level
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
----- Original Message -----
From: "Info 2004" <[EMAIL PROTECTED]>
To: "ICS support mailing" <email@example.com>
Sent: Thursday, May 25, 2006 10:19 AM
Subject: Re: [twsocket] HTTP serving large files problem
> Please. Does anyone have any suggestions on this?
> Info 2004 wrote:
>> I'm using the Webserv example within my app to send xml files that I
>> dynamically create. I initially used SendStream to send my xml back to
>> the client, but I have now switched to using AnswerString. The reason
>> being that some browsers seemed OK without HTTP headers in the reply,
>> but some not. This may be a bum steer though.
>> The problem I have now is that the 1.3M xml response takes 56 seconds to
>> turn up at the browser on my LAN, but only ever partly turns up over a
>> WAN connection.
>> Smaller files seem to make it OK.
>> The creation of the xml on the fly takes 10 sec, and if I send the same
>> data as a file, and not dynamically created, it takes 12 sec.
>> I'm not sure where to look next. Can anyone suggest some pointers?
> ASA Micros Ltd.
> 141 Wardle Road,
> OL12 9JA
> Tel: +44(0)1706 355057
> Company No. 4722262
> VAT No. 704044772
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be