[twsocket] HTTP Server creates extremly high CPU load

2011-06-30 Thread Lars Gehre
Hello all, I have a serious problem with the http server component from ICS7 (downloaded from the repository last week). I'm using the wininet api on the client side to open a (GET) connection to a ICS http Server. For certain reasons I need to query the HEAD in intervals (while the other get

Re: [twsocket] HTTP Server creates extremly high CPU load

2011-06-30 Thread Lars Gehre
I noticed one thing: This only happens if files are involved, for virtual documents it does not happen. For the http server demo it means you need to open Index.html or Form.html. Lars -Original Message- From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On

Re: [twsocket] HTTP Server creates extremly high CPU load

2011-06-30 Thread Arno Garrels
Lars Gehre wrote: I noticed one thing: This only happens if files are involved, for virtual documents it does not happen. I cannot reproduce it, 0.0% CPU here. I used the OverbyteIcsWebServ demo running on a Win7 quadcore. However if I download a file with Firefox (100 Mbit/s LAN) at around 6

Re: [twsocket] HTTP Server creates extremly high CPU load

2011-06-30 Thread Lars Gehre
Well I was a little to fast with my conclusion. It only happens to files in the demo because they have a proper header, the virtual documents only give a 404 for a HEAD request. The download is not of matter, the demo files are 500 bytes or so. And the server load stays as long as the client is

[twsocket] Showstopped bug in ICS

2011-06-30 Thread Éric Fleming Bonilha
Hi I believe I found a showstopper bug in ICS that lead my software to crash in many customers. The problem is with wsoNoReceiveLoop option from socket! In my program, I have to use wsoNoReceiveLoop in order to better process the data, I don´t want to process the data from the thread that

Re: [twsocket] HTTP Server creates extremly high CPU load

2011-06-30 Thread Lars Gehre
I think, I found something. The problem seems to be the head request. Normaly you do a HEAD and close the connection, but in my case it stays open and the http server gets stuck in an endless loop. The culprits are: procedure THttpConnection.SendDocument(SendType : THttpSendType;const