I have not read all the discussions, but at least this:
>- By the way: If you have no Line Mode then ICS don't do
> buffering at all. It just uses "send" of Winsock!
This sentence is wrong. TWSocket use a FIFO buffer when you call Send.
Whatever data size you send, TWSocket will use a list of bu
Thanks Maurizio. That did the trick, it works now. Fortunately the new ICS
(Version 5) hasn't affected anything in the current project, but I do have
older projects that I made modifications to the ICS code which I will have to
recode. That's why I hesitated at first to upgrade.
Robert.
--
Scrive robertoschler :
> I am using Delphi Professional 6.0 pack 2 with ICS. I'm not sure what
> version of ICS I am using since I don't see the version number in the README.
> However, I checked HttPProt.pas and the final comment reads:
>
> "Oct 15, 2004 V1.71 lotauro.mauri...@dnet.it enhanced
> If you reproduce my test, simply by compiling and starting server.pas
> and then
> compiling and starting client.pas with attached delphi debugger, looking
> on code
> line executed step, you can see that "socket.flush" forces to write out
> the data via
> the "send" call of winsock before it
I am using Delphi Professional 6.0 pack 2 with ICS. I'm not sure what version
of ICS I am using since I don't see the version number in the README. However,
I checked HttPProt.pas and the final comment reads:
"Oct 15, 2004 V1.71 lotauro.mauri...@dnet.it enhanced basic and NTLM
aut
>
>> - The clients wrote via "send" to somewhere about 16 Mbytes and if you
>> were true and it would be in buffer of the client then the process would
>> must have in Taskmanagers at least 16 MB of memory size. Please
>> look at my screenshot, the server and the client does have just 3.5 MB!
>>
PREFACE: The link on the certain pages on the Overbyte.be and nearly every
archived TWSocket mailing list message that is supposed to take you to the
mailing list sign up form is wrong:
Look at the FAQ page:
http://users.telenet.be/sonal.nv/ics/faq/Frame_index.html
Which has this link which le
> - The clients wrote via "send" to somewhere about 16 Mbytes and if you
> were true and it would be in buffer of the client then the process would
> must have in Taskmanagers at least 16 MB of memory size. Please
> look at my screenshot, the server and the client does have just 3.5 MB!
I'm not a
Hello!
> HI Piotr Dałek,
> yes you are right with your argumentation. I am using TWSocket in a manner
> generally not allowed, cause message processing and so on is not assured.
And we can stop right here.
Since I'm a ICS V5 user, I cannot answer to your "but"'s - maybe something
has changed in
HI Piotr Dałek,
yes you are right with your argumentation. I am using TWSocket in a manner
generally not allowed, cause message processing and so on is not assured.
BUT!
- The clients wrote via "send" to somewhere about 16 Mbytes and if you
were true and it would be in buffer of the client then
Hello!
> Hello ICS Mailinglist,
> this is a bugreport that on localhost the windows kernel reads megabytes
> of data
> before a TWSocket client can block. As you can see on the following
> explanation
> and the images on
> http://projekte.priv.de/ics_localhost_bug/
> , the problem is the wind
Hello ICS Mailinglist,
this is a bugreport that on localhost the windows kernel reads megabytes
of data
before a TWSocket client can block. As you can see on the following
explanation
and the images on
http://projekte.priv.de/ics_localhost_bug/
, the problem is the windows kernel:
"client_int
WOW! I have another prove for Buffering of Winsock! The used Memory is
NOT increasing
at alll! This means that the WINDOWS KERNEL is caching this!!!
>
>
>> Ok, this proves that Winsocks is buffering megabytes of data before
>> "TWSocket.pause" becomes active!
>>
>
> Not quite correct, TWSo
Markus Mueller wrote:
> Ok, this proves that Winsocks is buffering megabytes of data before
> "TWSocket.pause" becomes active!
Not quite correct, TWSocket.Pause becomes active immediately, however
winsock obviously continues to buffer incomming data, in this case I
think there's not much you ca
Hello Markus,
What is RAM usage then? How could Winsock buffer hundreds of MBs when you
don't read and flush the buffer? If it was correct, you should see process
RAM usage go up and up to the ceiling!!
Regards,
SZ
On Fri, Jan 23, 2009 at 7:52 PM, Markus Mueller wrote:
> Hello SZ,
>
> why the
Hello SZ,
why then the data comes through the WSocketGetProc('recv') function, in
WSocket_Synchronized_recv? This IS Winsock! And if I set a breakpoint
to this FRecv(s, Buf^, len, flags); then every thread running through this
function causes a stop on all threads!
Regards,
Markus Mueller
> AFAIK
AFAIK, Winsock buffers as much as only its buffer size data! It is ICS that
buffers data when you have paused it and when you press F8 on a breakpoint,
all threads run in the background.
HTH,
SZ
On Fri, Jan 23, 2009 at 7:41 PM, Markus Mueller wrote:
> Hello Arno Garrels and...
>
> Special Hell
Hello Arno Garrels and...
Special Hello to Francois Piette! Please look at the "@Francois Piette"
at the end of this mail!
>> This is exactly the point! I just don't get who reads the data, but
>> there is defintively
>> something reading all the available data (into a buffer?)!
>> Later I see
>>
Markus Mueller wrote:
> Hello (again :-)) Arno Garrels,
>>> I looked over the code of "THttpCli" and if you do not have a
>>> connection from localhost to localhost it may work... I expect this
>>> in particular cause the read of Megabytes is done within split
>>> seconds,
>>>
>> Yes, it is very f
Hello (again :-)) Arno Garrels,
>> I looked over the code of "THttpCli" and if you do not have a
>> connection from localhost to localhost it may work... I expect this
>> in particular cause the read of Megabytes is done within split
>> seconds,
>>
> Yes, it is very fast.
>
so you agree a
Markus Müller wrote:
> Hi Arno Garrels,
>
> I looked over the code of "THttpCli" and if you do not have a
> connection from localhost to localhost it may work... I expect this
> in particular cause the read of Megabytes is done within split
> seconds,
Yes, it is very fast.
> also if my program
Hi Arno Garrels,
I looked over the code of "THttpCli" and if you do not have a connection
from localhost to localhost it may work... I expect this in particular cause
the read of Megabytes is done within split seconds, also if my program is
sleeping (for example on a breakpoint in Delphi).
The pr
Markus Mueller wrote:
> it buffers sometime within 2-4 MByte before "socket.pause" does help,
> my
>> 3 Ghz Dualcore
> seems to buffer also hunderts of MByte...
procedure TCustomWSocket.Pause calls winsock API WSAAsyncSelect.
It simply tells winsock to stop posting notification messages.
"Altho
Test - Please ignore
--
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
24 matches
Mail list logo
