Something wrong in TIcsWndHandlerPool.GetWndHandler ?
--
[EMAIL PROTECTED]
http://www.overbyte.be
----- Original Message -----
From: "Fastream Technologies" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Saturday, June 10, 2006 9:20 AM
Subject: Re: [twsocket] ICSv6 Thread Attach/Detach problem
> Now I get this exception:
>
> function TIcsWndHandler.AllocateMsgHandler(Obj: TIcsWndControl): UINT;
> var
> I : UINT;
> begin
> if FMsgLow < WM_USER then
> raise EIcsException.Create('MsgLow not defined');
> if FMsgCnt >= WH_MAX_MSG then
> raise EIcsException.Create('No more free message'); // FIRED after
> a
> dozen page views!!!
> I := 0;
>
> Any idea?
>
> Regards,
>
> SZ
>
> ----- Original Message -----
> From: "Arno Garrels" <[EMAIL PROTECTED]>
> To: "ICS support mailing" <twsocket@elists.org>
> Sent: Friday, June 09, 2006 3:56 PM
> Subject: Re: [twsocket] ICSv6 Thread Attach/Detach problem
>
>
> : Fastream Technologies wrote:
> : > Please realize the async nature of the SELECT. Is there any way we
> : > change this to SYNC because it ruins synchronization.
> :
> : AFAIK winsock API function WSAAsyncSelect() is a common, blocking
> : function. In this case it's called to disable winsock notifications.
> : Because the window is detached/destroyed in subsequent lines.
> : BTW: Same is done in V5.
> : So for a short while the detached socket is windowless, that's
> : why I suggested to wait w/o processing messages until it is
> : attached again (not nice but worked for me). Haven't we talked
> : about the same problem in the SSL-list some months ago?
> :
> : ---
> : Arno Garrels [TeamICS]
> : http://www.overbyte.be/eng/overbyte/teamics.html
> :
> : >
> : > Regards,
> : >
> : > SubZero
> : >
> : > ----- Original Message -----
> : > From: "Fastream Technologies" <[EMAIL PROTECTED]>
> : > To: "ICS support mailing" <twsocket@elists.org>
> : > Sent: Friday, June 09, 2006 2:41 PM
> : > Subject: Re: [twsocket] ICSv6 Thread Attach/Detach problem
> : >
> : >
> : >> It worked here as well. But I have another guess: my case is a bit
> : >> different than what you demoed. In my case the client is connected
> : >> to a server while its thread is being changed. So,
> : >>
> : >> procedure TCustomWSocket.ThreadDetach;
> : >> begin
> : >> if (GetCurrentThreadID = DWORD(FThreadID)) and (FHSocket <>
> : >> INVALID_SOCKET) then
> : >> WSocket_Synchronized_WSAASyncSelect(FHSocket, Handle, 0, 0);
> : >> // THIS LINE IS CALLED
> : >> inherited ThreadDetach;
> : >> end;
> : >>
> : >> Could this be the problem? This code is called in
> : >> THttpCli.CtrlSocket.
> : >>
> : >> Best Regards,
> : >>
> : >> SZ
> : --
> : 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
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
--
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
