eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Tuesday, March 27, 2007 9:07 PM
Subject: Re: [twsocket] Architectural question II
> Arno Garrels wrote:
Arno Garrels wrote:
>>> What do you think?
>>
>> As stated above, by first opinion is simply to ignore older OS.
>
> That was my first idea as well, so yesterday I already implemented
> simple timers into OverbyteIcsWndControl.pas (ignoring .NET
> compatibility). It's currently part of TIcsWndCon
Arno Garrels wrote:
> That was my first idea as well, so yesterday I already implemented
> simple timers into OverbyteIcsWndControl.pas (ignoring .NET
> compatibility). It's currently part of TIcsWndControl and implemented
> as TCollection/TCollectionItem. If that is too much overhead for all
> cla
>> What do you think?
>
> As stated above, by first opinion is simply to ignore older OS.
That was my first idea as well, so yesterday I already implemented simple
timers into OverbyteIcsWndControl.pas (ignoring .NET compatibility). It's
currently part of TIcsWndControl and implemented as TColle
> That's true, however it does not solve the main problem with timers
> in ICS. The general problem with timers (beside the question which
> window to use) is that they are a limited resource.
As far as I know, timer are no more a limited resource sinceW2K.
> If we want support
> of "timer per in
Francois PIETTE wrote:
> In V6, this is a single window for all timers in a single thread.
> In V5, there is a window for each component and that window is used
> for the timer.
> So in both cases, there not a single hidden window dedicated to the
> timers.
That's true, however it does not solve
>>> I do not understand who shall handle the WM_TIMER messages?
>>> Currently TIcsWndControl skips message numbers below WM_USER,
>>> do you want to change that? WParam of WM_TIMER can hold a
>>> custom 32 bits value like an object reference.
>>
>> In V5, the component hidden window can handle the
Tobias Rapp wrote:
>> Something like attached below? It creates its window thread-save,
>> but I prefer a timer that was able to use the hidden window(s)
>> of V6, or may be we think about a windowless timer (Thread, signals,
>> and WaitForMultipleObjects)?
>
> Just for interest: What is the drawb
-
> From: "Arno Garrels" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> Sent: Thursday, March 22, 2007 10:21 AM
> Subject: Re: [twsocket] Architectural question II
>
>
>> Francois PIETTE wrote:
>>> We don't need a component
> Something like attached below? It creates its window thread-save,
> but I prefer a timer that was able to use the hidden window(s)
> of V6, or may be we think about a windowless timer (Thread, signals,
> and WaitForMultipleObjects)?
Just for interest: What is the drawback of using a own window
tuff for all components.
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Thursday, March 22, 2007 10:21 AM
Subject: Re: [twsocket] Architectural question II
> Francois PIETT
> To: "ICS support mailing"
> Sent: Wednesday, March 21, 2007 4:42 PM
> Subject: Re: [twsocket] Architectural question II
>
>
>> Francois Piette wrote:
>>>>>> Don't use TTimer in any worker thread since it is NOT thread-
>>>>>> safe
http://www.overbyte.be
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Wednesday, March 21, 2007 4:42 PM
Subject: Re: [twsocket] Architectural question II
> Francois Piette wrote:
>>>>> Don't use T
Francois Piette wrote:
Don't use TTimer in any worker thread since it is NOT thread-safe!
>>>
>>> Why is it used in HttpCli then ?
>>> see THttpCli.SendRequest
>>
>> That's true, I would not define UseBandwidthControl in multithreaded
>> applications until a thread-safe timer becomes availab
> >> Don't use TTimer in any worker thread since it is NOT thread-safe!
> >
> > Why is it used in HttpCli then ?
> > see THttpCli.SendRequest
>
> That's true, I would not define UseBandwidthControl in multithreaded
> applications until a thread-safe timer becomes available.
We could use a bare b
ailable.
--
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
> Paul
>
>
>
> - Original Message -
> From: "Arno Garrels" <[EMAIL PROTECTED]>
> To: "ICS support mailing"
> Sent: Wednesday, March 21, 2007 8:32 AM
>
007 8:32 AM
Subject: Re: [twsocket] Architectural question II
> Markus Humm wrote:
>> Hello,
>>
>> regarding my question from last weekend only a part was answered so
>> far. The thing is now: if several TTimers get fired at the same time
>> and all of them want
Markus Humm wrote:
> Hello,
>
> regarding my question from last weekend only a part was answered so
> far. The thing is now: if several TTimers get fired at the same time
> and all of them want to write into a shared TStringList-Type buffer
> (okay, it's in a wrapper class), how to make sure only
The "correct" way is to use a "semaphore". These do all the management
on exclusive resources. There are lots of classes out there to
download that implement.
Semephores are built-in to the operating system.
> Markus Humm wrote:
>> Hello,
>>
>> regarding my question from last weekend only a
Why not have a single thread responsible for doing that and then just
have the TTimers use PostThreadMessage to request the update?
Markus Humm wrote:
> Hello,
>
> regarding my question from last weekend only a part was answered so far.
> The thing is now: if several TTimers get fired at the sam
Hello,
regarding my question from last weekend only a part was answered so far.
The thing is now: if several TTimers get fired at the same time and all
of them want to write into a shared TStringList-Type buffer (okay, it's
in a wrapper class), how to make sure only one at a time gets acces and
21 matches
Mail list logo
