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

Reply via email to