When to use Indy TcpServer.IOHandler.WriteBufferOpen

Hi,

In our application I notice we are using IOHandler.WriteBufferOpen as follows:
On the client AND on the server we are doing something like this...

        Connection.IOHandler.WriteBufferOpen;
        try
          Connection.IOHandler.Write(   Some Stream Data    )
          Connection.IOHandler.WriteBufferFlush;
          Connection.IOHandler.WriteBufferClose;
        except
          Connection.IOHandler.WriteBufferCancel;
        end;

Our application is a typical client server application (an accounting software package actually) where the client sends small requests for data and the server returns varying size streams of data.

We are getting problems connecting to a server that is running on a very poor internet connection (3rd World Country - 256kbps internet).

A short packet of information such as the initial login works.  But then we get Read Timeouts when a slightly larger packet of information is being sent from the server to our client.  Interestingly, we don't get any problem sending huge data the other way (even with writebuffer used on our client) - I guess that is because our internet technology is much better.


I am most interested in QUESTION 2 (below) because I want to understand wny my developers may have used it.


Question 1 -  Should we get rid of the WriteBuffer code?

Question 2 - In what scenarios would you use WriteBuffer?

Question 3 - Please confirm - Setting UseNaggle:=false will not help?

Question 4 - Please confirm - Setting that ReuseSocket:=rsTrue will not help?