- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, February 05, 2006 2:15 PM
Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
> Fastream Technologies wrote:
>> Are
>> you using NOFORMS
es less that 5 minutes (incl.
porting it to BCB)!
Arno
> This is a reverse
> proxy.
>
> Regards,
>
> SZ
>
> - Original Message -
> From: "Arno Garrels" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> Sent: Sunday, February 05,
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Sunday, February 05, 2006 1:41 PM
Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
> Fastream Technologies wrote:
>> I agree with you in your both emails BUT e
egards,
>
> SZ
>
> - Original Message -
> From: "Arno Garrels" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> Sent: Saturday, February 04, 2006 5:38 PM
> Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
>
-
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Saturday, February 04, 2006 7:40 PM
Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
> Fastream Technologies wrote:
>> Yes it is called in my beta as well but the o
CTED]>
> To: "ICS support mailing"
> Sent: Saturday, February 04, 2006 7:05 PM
> Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
>
>
>> It looks like you have an old HttpProt version.
>> SetWindowLong is correctly called in my code
rom: "Fastream Technologies" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> Sent: Saturday, February 04, 2006 3:41 PM
> Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
>
>
>>I found the ICS bug: when I put the below in the ThttpCli des
ent: Saturday, February 04, 2006 3:41 PM
Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
>I found the ICS bug: when I put the below in the ThttpCli descendent's
> destructor, it works:
>
> SetWindowLong(FWindowHandle, 0, 0);
>DestroyWindow(FWin
ROTECTED]>
To: "ICS support mailing"
Sent: Saturday, February 04, 2006 5:38 PM
Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
> BTW: Also this returns TRUE for both windows:
>
> function XSocketDeallocateHWnd(Wnd: HWND): boolean;
> begin
>Resu
se). I've my doubts that order of
> destroying the windows matters, but not 100% sure.
>
> ---
> Arno Garrels [TeamICS]
> http://www.overbyte.be/eng/overbyte/teamics.html
>
>
>> Best Regards,
>>
>> SZ
>>
>> ----- Original Message -----
>
"ICS support mailing"
> Sent: Saturday, February 04, 2006 1:28 PM
> Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
>
>
>> Fastream Technologies wrote:
>>> Hello,
>>>
>>> That bug caused a lot of frustration here. Now the p
mailing"
Sent: Saturday, February 04, 2006 1:28 PM
Subject: Re: [twsocket] Remember the SetWindowLong bug in WSocket?
> Fastream Technologies wrote:
>> Hello,
>>
>> That bug caused a lot of frustration here. Now the problem is resolved
>> for
>> FTP and web
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
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. XWindowDealloc returns true but I have BIG
14 matches
Mail list logo
