Re: [twsocket] Remember the SetWindowLong bug in WSocket?

2006-02-04 Thread Arno Garrels
Fastream Technologies wrote: > Hello, > > That bug caused a lot of frustration here. Now the problem is resolved for > FTP and web servers with my fix BUT for the reverse proxy, there is a > window leakage that cannot be detected by CodeGuard. It seems the problem > is in THttpCli destructor. XWin

Re: [twsocket] Remember the SetWindowLong bug in WSocket?

2006-02-04 Thread Fastream Technologies
I found the ICS bug: when I put the below in the ThttpCli descendent's destructor, it works: SetWindowLong(FWindowHandle, 0, 0); DestroyWindow(FWindowHandle); SetWindowLong(FCtrlSocket->Handle, 0, 0); DestroyWindow(FCtrlSocket->Handle); In THttpCli destructor, the destruc

Re: [twsocket] Remember the SetWindowLong bug in WSocket?

2006-02-04 Thread Arno Garrels
Fastream Technologies wrote: > I found the ICS bug: when I put the below in the ThttpCli descendent's > destructor, it works: > > SetWindowLong(FWindowHandle, 0, 0); > DestroyWindow(FWindowHandle); > SetWindowLong(FCtrlSocket->Handle, 0, 0); > DestroyWindow(FCtrlSocket->Han

Re: [twsocket] Remember the SetWindowLong bug in WSocket?

2006-02-04 Thread Arno Garrels
BTW: Also this returns TRUE for both windows: function XSocketDeallocateHWnd(Wnd: HWND): boolean; begin Result := (SetWindowLong(Wnd, 0, 0) <> 0) and DestroyWindow(Wnd); end; Arno Garrels wrote: > Fastream Technologies wrote: >> I found the ICS bug: when I put the below in the ThttpCli desce

Re: [twsocket] Remember the SetWindowLong bug in WSocket?

2006-02-04 Thread Fastream Technologies
I agree with you in your both emails BUT emprically it works in the way I wrote. Try creating and destroying 1000 httpclients with NOFORMS and you will see that you will be wasting more than 20MB of RAM!! Regards, SZ - Original Message - From: "Arno Garrels" <[EMAIL PROTECTED]> To: "I

Re: [twsocket] Remember the SetWindowLong bug in WSocket?

2006-02-04 Thread Francois PIETTE
It looks like you have an old HttpProt version. SetWindowLong is correctly called in my code (that is the last beta). -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: "Fastream Technologies" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Saturday, February 04,

Re: [twsocket] Remember the SetWindowLong bug in WSocket?

2006-02-04 Thread Fastream Technologies
Yes it is called in my beta as well but the ordering is not right. Ctrlsocket should be freed later. Regards, SZ - Original Message - From: "Francois PIETTE" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Saturday, February 04, 2006 7:05 PM Subject: Re: [twsocket] Remember the Se

Re: [twsocket] Remember the SetWindowLong bug in WSocket?

2006-02-04 Thread Arno Garrels
Fastream Technologies wrote: > Yes it is called in my beta as well but the ordering is not right. > Ctrlsocket should be freed later. That may be correct, only I do not understand why. Does a reverse creation order fix the leak as well? In THttpCli.Create, allocating FWindowHandle after CreateSock

Re: [twsocket] Remember the SetWindowLong bug in WSocket?

2006-02-04 Thread Fastream Technologies
What I think is more radical: I think we should get rid of window handles all together! (except one per thread). So v6 is the way to go but I see development slowed down. I talked with Peter and he promised to get the v5 Digest auth http server code ready by Monday. When we translate it to v6,

[twsocket] Spiders

2006-02-04 Thread David Colliver
Hi all, Slightly OT but has anyone created a spider, crawler, bot - whatever you like to call it using TWSocket? If so, please mail me off list. I have some questions that are likely to be OT. Best regards, Dave Colliver. http://www.AshfieldFOCUS.com ~~ http://www.FOCUSPortals.com - Local franc