> don't hardcode 64Kb buffers inside inet.c, don't set any kind of buffer there, > simply use what the OS has as default buffer and do 1.4Kb reads/writes as it > was before (BTW, previous code worked for everyone for several years, so it > cannot be so bad). > > Then, inside ftp code, or your own code, using your just added > > InetSetSndBufSize( pSocket, nSizeSendBuffer ) > InetSetRcvBufSize( pSocket, nSizeReciveBuffer ) > > InetGetSndBufSize( pSocket ) > InetGetRcvBufSize( pSocket ) > > functions set send/receive buffer to what you like/think can be best for you. >
I agree with this point. Probably, it will be useful also to have a possibility to change that 1.4kb packet limit. When Miguel wrote about this issue first time, I thought that he want to change this limit, not the internal. Personally I don't understand, through, why this 1.4kb limit is needed at all, if we have already internal socket buffer size. It would be nice to hear original author arguments. Regards, Alexander. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
