Angus Robertson - Magenta Systems Ltd wrote:
I dont think the control channel of FTP needs throttling, only data
channel.
Who would possible want to throttle even the data channel on a FTP client?
For instance someone who wants to be able to trottle down CPU load on very fast
connections.
Hello Francois,
OK, so may be I could take care about OnSendData to avoid Winsock
getting to much data in buffer (remembering that toses data could only
feet in 1/4 physical limited RAM size).
May .send loop for the 5.000 users overload the buffer and crash
system ?
If yes then I
Hello,
Mistaken... s/OnSendData/OnDataSent
D OK, so may be I could take care about OnSendData to avoid Winsock
D getting to much data in buffer (remembering that toses data could only
D feet in 1/4 physical limited RAM size).
--
To unsubscribe or change your settings for TWSocket mailing
What is the number of sockets 32-bit Windows can handle with the maximum 4GB
of memory?
Regards,
SZ
- Original Message -
From: Dod [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Wednesday, January 18, 2006 10:25 AM
Subject: Re: [twsocket] fast data sending
One reason would be that the client does not want to soak up all the
bandwidth. For example, I routinely run an RDP session over my
Internet connection. It would be nice to also do some low-level
downloading with FTP -- generally I cannot because the FTP client gets
data at the limit of my
Hello Fastream,
Well, after some discussions here it appear there is a limitation of
1/4 of physical memory with max of 256MB (more on 64bit Windows) if I
am right.
Then you should count with max handle windows can manage (about 10.000
standard and 18.000 with registry tricks).
Then you
Hello,
Then you should count with max handle windows can manage (about 10.000
standard and 18.000 with registry tricks).
FT Is this valid also for v6?
V6 don't need one handle per socket anymore.
But seems that Winsock itself uses 3 handles per socket, this is at
least what I saw in my
Hello,
Then you must divide memory with ram size occupied per socket, some
reported about 6KB average, my own tests showed rather 10KB. Not
counting all other processes/drivers that may allocate memory in this
segment.
FT Is this paged memory or non-paged also ok?
Sorry I mistaken,
- Original Message -
From: Dod [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Wednesday, January 18, 2006 11:35 AM
Subject: Re: [twsocket] fast data sending
But seems that Winsock itself uses 3 handles per socket, this is at
least what I saw in my project
hi everyone,
i'm wondering if the following behavior is usual or not :
i'm trying to connect to a website on a tcp port that i know won't work.
here' what i receive :
==OnStateChange : httpClosing
==OnStateChange : httpReady
==RequestDone : httpABORT - ErrCode=0 - Status Code : 200
hello,
is it already possible to install this beta version for the C++ Builder
of BDS 2006?
when i try to open the Package: OverbyteIcsDel100Package.bdsproj
or OverbyteIcsDel100Package.dpk
i get the error of a missing Delphi.Personality.
anyway do i not know, if it is possible to open these
Hello Fastream,
You can easely create thousands of TTimers, but you have to taken all
limits into account. From the moment you enable a TTimer a hidden window
is created. disabling the TTimer also destroy that window. So the window
is only there for a short time (while TTimer is running).
On the
Hello Dod,
To be as correct as possible:
- TWSocket used no non-pagable memory, neahter does his buffers.
- Only Winsock does use it for the socket, for send and for receive.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
--
To
I think the limit for handles is for window handles and the handles
created by Winsock are not windows.
Yes this limit is the limit of windows. Not the limit of handles. Sure
somewhere there could be a limit of handles, but I espect this is only a
limit so high that we does not have that to
Wilfried Mestdagh wrote:
Hello Fastream,
You can easely create thousands of TTimers, but you have to taken all
limits into account. From the moment you enable a TTimer a hidden window
is created. disabling the TTimer also destroy that window. So the window
is only there for a short time
Each throttler requires a different interval. Perhaps a timer of 1ms
interval can cover all?
Regards,
SZ
- Original Message -
From: Dod [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Wednesday, January 18, 2006 5:00 PM
Subject: Re: [twsocket] fast data sending
- Original Message -
From: Dod [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Wednesday, January 18, 2006 5:20 PM
Subject: Re: [twsocket] fast data sending
Hello,
FT Each throttler requires a different interval. Perhaps a timer of 1ms
FT interval can cover all?
Original Message
From: Arno Garrels [EMAIL PROTECTED]
I've just more or less copied and pasted the bandwidth control stuff
from HttpProt.pas to FtpProt.pas, enabled it on the data channel only
so far. I couldn't find a note who contributed this code?
Also, should I enable it on the
Each throttler requires a different interval. Perhaps a timer of 1ms
interval can cover all?
I think you'll find that windows timers and GetTickCount only have a
resolution of about 20ms, which is also how often your threads get CPU
time.
Angus
--
To unsubscribe or change your settings
Peter Feldbaumer wrote:
Could I suggest to create a descendent component from TFtpSrv - something
like TFtpSrvThrottled - to implement bandwidth-limiting?
The current implementation (if it is like in HttpProt.pas) doesn't fit my
needs (and probably that of others, too) - e.g. if one needs
Original Message
From: Arno Garrels [EMAIL PROTECTED]
Current implementation is in the FTP/HTTP _clients_ only, conditional
compiled. It probably won't fit my needs in real world applications as
well.
A derived throttled server would be nice, however nicer would be a
Hello,
Each throttler requires a different interval. Perhaps a timer of 1ms
interval can cover all?
I dont know the limit of windows timers, but indeed 1 timer can cover
all timings. 1 ms is not realistic because of the time slice of winows.
Workstations OS has time slice of 13 ms or something
Hi.. Friends..
How i implement a timeout control in HttpCli...
I using HttpCli in sync mode, because i need to run it in Thread..
It's work fine, but in some(rare) cases httpcli freeze and no get any
response...
How i cancel httpcli get/post command? after started?
Thanks
I think theres already one in my zip, but Im not 100% sure.
Dan
- Original Message -
From: Peter Feldbaumer [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Wednesday, January 18, 2006 3:30 PM
Subject: Re: [twsocket] Bandwidth control TFtpClient
Original
I have a problem sending large block of data. It's a binary string of 32696
bytes. It seems that only 3 bytes are send/received, rest is cut off. Is
there a need of sending smaller chunks and use ondatasent or is there somewhere
a hidden parm I need to adjust? I'm not even sure if the
I am using ICS, the components I use are TWSocketServer and TWSocket. I try to
send a large string with
Display(IntToStr(SendStr(Encrypt(AnswerData.CommaText) + #13#10))+'bytes sent');
CloseDelayed;
The bytecount tells me that all is sent. But on the receive it is cut of...
procedure
Hello,
I need to send a bunch of data, in size of about 7 Kilobytes,
if I sent it all at once using client.Send(@fm, sizeof(fm)); the client
cannot always receive it succesfully, sometimes it is received all at once,
but sometimes the client received only 1,5 Kilobytes
If I sent it in 5
Hi,
If you were using TCP, then it was correctly received.
You have to create you only routine for sending and receiving the data,
with header to indicate the buffer length send out.
Regards
KL CHin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Surabaya
Yes, I think I used TCP since I'm using TWSocketServer
On 1/19/06, KL Chin [EMAIL PROTECTED] wrote:
Hi,
If you were using TCP, then it was correctly received.
You have to create you only routine for sending and receiving the data,
with header to indicate the buffer length send out.
Hi Surabaya,
As mentioned early, you have to create your own protocol to
send and receive data, bcoz TCP does not have the fix-ed
packet size received.
So you have to send a header out to tell the total bytes to be
send, and the receiving end have to base on this header to
receives all the data
30 matches
Mail list logo
