> 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.
Making changes in ICS components is never a good idea unless you dis
Hi Francois Piette,
>> - 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 buffers (Each
> having a
Hi RTT,
which Operationgsystem and Pachlevel are you using? Do you
use ICS Version 6 RC1 ? I am using Windows XP with
Service Pack3, tested my Client now on 3 Clients with this config.
I am using ICS Versoin 6 at RC1. I added my client.exe and
server.exe on my server http://projekte.priv.de/ics_lo
Markus Mueller wrote:
> Hello ICS Mailinglist,
>
> this is a bugreport that on localhost the windows kernel reads
> megabytes of data
> before a TWSocket client can block.
This is not specific to TWSocket and it's not a bug but a winsock
feature!
Beside the fact that you should send smaller data
Hi Arno Garrels,
>> this is a bugreport that on localhost the windows kernel reads
>> megabytes of data
>> before a TWSocket client can block.
>>
>
> This is not specific to TWSocket and it's not a bug but a winsock
> feature!
> Beside the fact that you should send smaller data chunks and use
Markus Mueller wrote:
> I missed to tell that my sentence is only valid if you do
> "TWSocket.Flush;".
> And there I am true that V6 ICS directly runs "send" on Winsock to
> immediatlely
> send the data. And that was the point: It not buffers internaly but
> forces to send
> it immediately to wins
> And there I am true that V6 ICS directly runs "send" on Winsock to
> immediatlely send the data. And that was the point:
> It not buffers internaly but forces to send
> it immediately to winsock or it blocks.
I don't agree, unless a bug has been introduced recently.
Send only TRIES to send data.
> Any idear why on my Computers it shows
> but on your computer it blocks much earlier?
Maybe be you some kind of proxy, firewall, anti-virus, anti-spam, malware,
LSP, VPN and other kind of similar piece of software intercepting TCP trafic
and buffering data somewhere.
--
francois.pie...@overby
Francois PIETTE schrieb:
>> And there I am true that V6 ICS directly runs "send" on Winsock to
>> immediatlely send the data. And that was the point:
>> It not buffers internaly but forces to send
>> it immediately to winsock or it blocks.
>>
>
> I don't agree, unless a bug has been introduced
Markus Mueller wrote:
> Hi Arno Garrels,
>>> this is a bugreport that on localhost the windows kernel reads
>>> megabytes of data
>>> before a TWSocket client can block.
>>>
>>
>> This is not specific to TWSocket and it's not a bug but a winsock
>> feature!
>> Beside the fact that you should send
> Hi RTT,
>
> which Operationgsystem and Pachlevel are you using? Do you
> use ICS Version 6 RC1 ? I am using Windows XP with
> Service Pack3, tested my Client now on 3 Clients with this config.
> I am using ICS Versoin 6 at RC1. I added my client.exe and
> server.exe on my server http://projekte.
Hello ICS,
I found the problem, it was
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpWindowSize
set to 16 Mbyte on my Windows Systems.
Thanks for your support and your time! You have helped me very very much!
Much regards,
Markus Mueller
>> Hi RTT,
>>
>> which Operat
Yes I learned some things reading your thread. Anyway, just checked
with regedit and my Vista x64 registry has no such key. What is the
default value?
Regards,
SZ
On Sat, Jan 24, 2009 at 1:41 PM, Markus Mueller wrote:
> Hello ICS,
>
> I found the problem, it was
>
> HKEY_LOCAL_MACHINE\SYSTEM\Cu
The default is that it is not configured. Cause tcp window scaling is also
deactivated, I asume it uses the "normal" tcp maximum of 64 Kbyte.
Without the "Tcp1323Opts" for Windows scaling a higher TCP Window
Size don't make sense at all. For more informations see
http://proj.sunet.se/E2E/tcptune.
Hi Arno Garrels,
> Markus Mueller wrote:
>
>> The default is that it is not configured. Cause tcp window scaling is
>> also deactivated, I asume it uses the "normal" tcp maximum of 64
>> Kbyte.
>>
>> Without the "Tcp1323Opts" for Windows scaling a higher TCP Window
>> Size don't make sense at a
Markus Mueller wrote:
> The default is that it is not configured. Cause tcp window scaling is
> also deactivated, I asume it uses the "normal" tcp maximum of 64
> Kbyte.
>
> Without the "Tcp1323Opts" for Windows scaling a higher TCP Window
> Size don't make sense at all. For more informations see
Markus Mueller wrote:
> Correct, beside the maximum limit of 65,353 in detail: With TCP Window
> Scaling (RFC 1323) you can use values up to two Gigabytes. But, as
> I sayed, you have to enable This option via Tcp1323Opts. And both, the
> client as well as the server, must support this TCP option.
Is just with me or something is not working?
Some of my messages/replies simple don't hit the list, and some others
don't show up in the archive.
I also noted other members messages I received today are not show in the
archive too!
RTT
--
To unsubscribe or change your settings for TWSocket mail
> Correct, beside the maximum limit of 65,353 in detail: With TCP Window
> Scaling (RFC 1323) you can use values up to two Gigabytes.
I read 1GB
From RFC1323:
"Since the max window is 2**S (where S is the scaling shift count) times
at most 2**16 - 1 (the maximum unscaled window), the maximum w
Hi RTT;
hehe, okay, you're right. :-)
Regards,
Markus Mueller
>> Correct, beside the maximum limit of 65,353 in detail: With TCP Window
>> Scaling (RFC 1323) you can use values up to two Gigabytes.
>>
> I read 1GB
>
> From RFC1323:
> "Since the max window is 2**S (where S is the scaling sh
20 matches
Mail list logo
