Re: [twsocket] Bandwidth control at the root (TCustomWSocket)
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 a timer? I don't think so. If it was impossible it's probably better to add bandwidth control to the upper level protocol components only, copying existing code from the FTP and HTTP clients? -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Bandwidth control at the root (TCustomWSocket)
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. Yes, it is possible and even easy ! You create a thread which sleeps the required time and then post a message. This would be much like a TTimer without an actual TTimer. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Bandwidth control at the root (TCustomWSocket)
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 a timer? I don't think so. Yes, it is possible and even easy ! You create a thread which sleeps the required time and then post a message. This would be much like a TTimer without an actual TTimer. OK, but was it cheaper than TIcsTime? -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Bandwidth control at the root (TCustomWSocket)
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. Yes, it is possible and even easy ! You create a thread which sleeps the required time and then post a message. This would be much like a TTimer without an actual TTimer. OK, but was it cheaper than TIcsTime? I have not TIcsTime code in my head... -- francois.pie...@overbyte.be http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Bandwidth control at the root (TCustomWSocket)
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 Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Bandwidth control at the root (TCustomWSocket)
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 a timer? I don't think so. Yes, it is possible and even easy ! You create a thread which sleeps the required time and then post a message. This would be much like a TTimer without an actual TTimer. OK, but was it cheaper than TIcsTime? I have not TIcsTime code in my head... Sorry typo, should read TIcsTimer. It works like TTimer however does not create a window to receive WM_TIMER messages but uses an existing ICS-window instead. 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. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Bandwidth control at the root (TCustomWSocket)
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 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? -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
