Hello,
I finally got it working now by using (and somewhat enhancing) that
thread approach.
I've left out the cancelling on long lasting connection attempts right
now, maybe I add it later and I think I might want to do it on shutdown
as well.
Greetings
Markus
--
To unsubscribe or change yo
I see this in procedure THttpConnection.SendStream;
{$IFDEF USE_SSL}
BufSize := 8192; { Only for testing }
{$ENDIF}
purpose ?
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.over
Fastream Technologies wrote:
> Hello,
>
>> HomeDir is hardcoded C:\TEMP.
> In order to test Windows security try the following:
> 1) Create a new user Group "FTP-Users"
> 2) Right-click Drive C: | Properties | Security-Settings
> 3) Add group FTP-Users deny "Full Access"
> 4) Go to C:\Temp, Proper
Hello,
> HomeDir is hardcoded C:\TEMP.
In order to test Windows security try the following:
1) Create a new user Group "FTP-Users"
2) Right-click Drive C: | Properties | Security-Settings
3) Add group FTP-Users deny "Full Access"
4) Go to C:\Temp, Properties | Security-Settings
Set proper NTFS r
Fastream Technologies wrote:
> Hello Arno,
>
> Just found time... Sorry. I have an idea, to reduce the "NTLM context
> switches",
It is the user security context that is switched. Currently
LogOnUser API is called once on login at the application level.
> why don't we increase the buffer size
Hello Arno,
Just found time... Sorry. I have an idea, to reduce the "NTLM context
switches", why don't we increase the buffer size from 1460 bytes to 8KB?
That's what I did with my copy and speed increased ~30%! I think obeying
Ethernet buffer size is less important than obeying Winsock buffer siz
