Francois,
Thank you for the reply.
I did actually get a web page to be sent, but what I did was load a web page
with
Stream->LoadFromFile(); So I am not sure why the dynamic virtual page was not
sent.
If you could send me the compiled version then I could test it and see if it
works.
I am usin
Fastream Technologies wrote:
> Arno,
>
> There is a TWndControl in the worker thread context which is created
> before clients are threadattach'ed to the thread (in a custom message
> handler).
I still recommend to find the sender of that anonymous message as well
as find a reliable range of mess
Arno,
There is a TWndControl in the worker thread context which is created before
clients are threadattach'ed to the thread (in a custom message handler).
Regards,
SZ
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Monday, February 05, 20
Fastream Technologies wrote:
> Yoiu also missed that this is a service application thread with no
> other component than ICS! Even no GUI. I am unable to find the bug--
> there is one I know but it happens under heavy load and does not show
> its ugly head under Debug compilation.
>
> It is just a
Yoiu also missed that this is a service application thread with no other
component than ICS! Even no GUI. I am unable to find the bug--there is one I
know but it happens under heavy load and does not show its ugly head under
Debug compilation.
It is just a simple constant, why shouldn't it be 8
Fastream Technologies wrote:
> Yes these are all what I thought for a week time! I call GetMessage,
> then check for known/my messages. If none of them, call
> dispatchmessage and all works fine except the problem which goes away
> if we set the WHG_MAX to 800 instead of 100! Now there is no such
>
Yes these are all what I thought for a week time! I call GetMessage, then
check for known/my messages. If none of them, call dispatchmessage and all
works fine except the problem which goes away if we set the WHG_MAX to 800
instead of 100! Now there is no such exception thrown--tested with milli
>> This is probably because you post custom messages do you?
>
> Yes but they are starting from WM_USER and there are only 4 of them
> in this thread. According to help, WM_USER starts from 0x0800 and
> there should be enough room until WM_APP+100.
But there must somebody send messages in that ra
Hello Arno,
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Monday, February 05, 2007 1:24 PM
Subject: Re: [twsocket] Possible bug and solution in TWndControl
> Fastream Technologies wrote:
>> Hello,
>>
>> When I use the following thread co
Fastream Technologies wrote:
> Hello,
>
> When I use the following thread code:
>
> void __fastcall ReverseProxyClientThread::Execute()
> {
> // Place thread code here
> FreeOnTerminate = true;
>
> ...
>
> TIcsWndHandler *windowHandler = new TIcsWndHandler();
> windowHandler->MsgLo
Hello,
When I use the following thread code:
void __fastcall ReverseProxyClientThread::Execute()
{
// Place thread code here
FreeOnTerminate = true;
...
TIcsWndHandler *windowHandler = new TIcsWndHandler();
windowHandler->MsgLow = WM_APP + 100;
while(!Terminated)
messagePump();
> >> good to know but thats not the clean way.
> >> and needs some additional cpu cycles on every headerline of course.
> FP> The clean way to add features you need is to derive your own component
from
> FP> ICS component and add what you need in that derived component. I agree
to do
> FP> slight
12 matches
Mail list logo
