: Monday, July 20, 2009 8:39 PM
Subject: Re: [twsocket] Bandwidth control at the root (TCustomWSocket)
Francois PIETTE wrote:
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
Arno Garrels wrote:
I don't think it could be a problem. But f it does, GetQueueStatus
can be called to know if there is a WM_TIMER message already in the
queue.
Did some testing with sending 1000 SendNotifyMessages to the main
thread per second. Then I paused message processing for 10
Arno Garrels wrote:
Arno Garrels wrote:
I don't think it could be a problem. But f it does, GetQueueStatus
can be called to know if there is a WM_TIMER message already in the
queue.
Did some testing with sending 1000 SendNotifyMessages to the main
thread per second. Then I paused message
Francois PIETTE wrote:
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
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 it was possible without using
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
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 it was possible without
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
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
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 it was possible without
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 sorted
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.
--
francois.pie...@overbyte.be
http://www.overbyte.be
--
To
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?
Regards, Fredrik.
--
To unsubscribe or change your settings for TWSocket mailing list
13 matches
Mail list logo