Hi!
I have a throughput/performance problem using the latest stable version
of the ICS package. When using a TWSocket derived application over an
TCP/IP connection with high round trip times and small packet sizes (it
is an 155 MBit ATM line) the throughput is very low. To check, if there
is a
Hello Tobias,
Are you using ICS in sync or async mode ?
Do yo use same buffer and write-to-disk as Indy ?
Do you use multi-threading or not ?
Is it binary or text file (I guess it is text file as you said long
line in the subject ?
Regards.
TR I have a throughput/performance problem using
Hello Dod,
Are you using ICS in sync or async mode ?
I'm using ICS in async (event driven) mode in my application. The file
is sent in fragments of 256KB in the OnDataSent event handler.
Do yo use same buffer and write-to-disk as Indy ?
When comparing ICS and Indy I did not use my
Hello Tobias,
Do you see any CPU overload server side during transfert ?
regards.
--
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.overbyte.be
Hello,
I think I found a bug in Java and/or ICS: I guess while testing you did not
set the auth mode to daBoth. Set it and try with the helloworld applet! Java
sends a HEAD request which is well authenticated and then sends a GET with
missing info and it stalls!!! As a workaround, I set damode
Sorry but I don't understand the link with the message you reply to.
--
[EMAIL PROTECTED]
http://www.overbyte.be
- Original Message -
From: Fastream Technologies [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Friday, January 12, 2007 12:38 PM
Subject: Re: [twsocket]
Hello,
Sorry, I still have fever. What I am talking about is HTTP/1.1 digest
authentication bug (which was my original problem). If you set the demo
component property to daboth, you can easily see.
Best Regards,
SZ
- Original Message -
From: Francois Piette [EMAIL PROTECTED]
To:
Hello Dod,
Do you see any CPU overload server side during transfert ?
CPU load varies from 2% to 5% while the FTP file transfer is running.
/Tobias
--
NOA Audio Solutions Vertriebsges.m.b.H.Tel: +43-1-5452700
Johannagasse 42/4 Fax: +43-1-545270014
A - 1050 Wien
Hello,
I did a quick look. It seems you start (or resume one from pool) a
thread and give the received data to it.
Probably you give data again to a thread that is still busy with the
previous data. You have to check for this somewhere because you tell
about corrupted data with many threads.
Hello Bevan,
It is normal that you receive an empty string once a while. Just exit
the OnDataAvailable event in that case. When data is really ready to
receive OnDataAvailable will fire again.
About the 10035 yo dont have to worry. This is internally handled by
TWSocket.
---
Rgds, Wilfried
Hello Tobias,
TCP/IP connection with high round trip times and small packet sizes
If packets are max MCU then Nagle will come in and will wait a while
to see if you want to send a packet again. Nagle does this to try to
concat packets to a larger one to fit into the max packet size.
Specially
Dear community,
a critical situation forces me to implement a quick way for sending
mailings with ICS components (all other stuff out there won't work
properly, they told me). In fact, it is a rather simple scenario -
walking through a customer database and sending SMTP mails to some
Using FtpTst demo, I upload a file from c:\dir, size 61,184. After upload,
size indicates 60995. Download the same file, size is 61,440.
Anybody know what's going on? I need the sizes to be same on
upload/download.
--
To unsubscribe or change your settings for TWSocket mailing list
please
Hi Michael,
Sorry, I sent my previous reply directly to you instead of to the list.
thanks for the hint, I already looked into the code and - by the way - I
find it very well structured. However, one question is left. ThereĀ“s
always spoken about using async components, but in my special case
Hi Wilfried,
It is normal that you receive an empty string once a while. Just exit
the OnDataAvailable event in that case. When data is really ready to
receive OnDataAvailable will fire again.
I see your point - the other day I got the same result over and over again,
today the same code
15 matches
Mail list logo