Yeah, I guess so. I had to look LSP - Layered Service Provider... :) I have
used it myself to limit some applications bandwidth to a max limit. But it
makes sense that it's an LSP-app.
-Original Message-
> I know that a permanent fix at componentlevel is desired but until
> that is sorte
I'm still not sure what was the best implementation in TCustomWSocket.
Anything speaking against your timer-based code in HttpProt.pas?
Since W2K there are plenty of timers possible.
For cilent application, there should be no problem. But for a server
application with potentially hundreds or th
Francois PIETTE wrote:
>> I've got it working without a timer by calling
>> MsgWaitForMultipleObjects to defer subsequent call of Resume
>> after Pause, however that seems to be a dangerous game. What do
>> you thing?
>
> Not good, the message pump must be called.
>>>
Fredrik Larsson wrote:
> Hi,
>
> I know that a permanent fix at componentlevel is desired but until
> that is sorted out perhaps you would want to use something such as
> http://www.netlimiter.com/ to limit the traffic the application uses?
Interesting tool, I guess it's a LSP isn't it?
--
Arno
I've got it working without a timer by calling
MsgWaitForMultipleObjects to defer subsequent call of Resume after
Pause, however that seems to be a dangerous game. What do you
thing?
Not good, the message pump must be called.
Do you think it was possible without using a timer? I don't think s
Francois PIETTE wrote:
I've got it working without a timer by calling
MsgWaitForMultipleObjects to defer subsequent call of Resume after
Pause, however that seems to be a dangerous game. What do you
thing?
>>>
>>> Not good, the message pump must be called.
>>
>> Do you think
I've got it working without a timer by calling
MsgWaitForMultipleObjects to defer subsequent call of Resume after
Pause, however that seems to be a dangerous game. What do you thing?
Not good, the message pump must be called.
Do you think it was possible without using a timer? I don't think so
