Hello Jan,

I am one of the STinG developers, and I want to report a marked change for
the worse in the performance of aFTP 1.51b as compared to older versions.
For uploads I now find it impossible to achieve better transfer rates than
appx 1024 cps.  The rate seems totally unaffected by any changes I make
in the STinG TCP settings or the physical bitrate.

Even at a rate as high as 153600 bps, connected locally to an FTP server
under STinG, the effective transfer rate for aFTP uploads remains around
1024 cps.  Other FTP clients do not have this problem, even though they
too have not been optimized for STinG (just like aFTP hasn't).

I really think that there is something fundamentally wrong in how this
current aFTP beta performs the uploads.


Apart from this problem I greatly appreciate the many nice features of
aFTP, especially the ease of use gained through the D&D interface, that
makes it possible for aFTP windows leading to remote LAN machines to be
used almost as normal directory windows of Thing. Very nice indeed !

