Waiting for server

Question

Why am I eternally waiting for the server when I'm trying to upload tiny text files to a web site with a perfectly good connection? This happens all the time. One minute I'm waiting until the connection times out and the next it's perfectly fast. What's the point in using Dreamweaver if it can't upload to a server? It's mostly useless otherwise. Transmit works ten times faster and is much more reliable and cheaper. Why can't Adobe simply buy Transmit and stick their code into Dreamweaver, since there is nobody at Adobe who actually knows how to program anything. They're all too busy trying to look cool while making long-winded videos.

Answer 1

Under Edit --> Preferences --> Site  I have experimented with FTP disconnect (idle)  and FTP time out high values low values - I am currently set to disconnect after 0 minutes idle and 60 second on the time out.
Many people have tested and Adobe should put a FTP log sniffer on the FTP process and look at ever command in the Upload to see where and why the FTP process hangs up.  Why does it fail some times and work other times.  It can fail on the 1st FTP after restating the PC, opening DW only and doing a post.  The FTP in the DW Log is insufficient and does not record the full process or if it does, the log is out of sequence with the actual events.
I ran a put on a small directory - the DW FTP log shows all files transferred. On the server, I could see that the files were all updated, yet DW was hung up with a message waiting on server and the lower right status line had an icon under Files and a message - Sometimes during a get when the local file is open in DW and is also selected as part of a multi-file download, DW pops up a dialog box warning of the loss of changes (the dialog box is behind the  background activities window and is not visible, unless one mouse's over the   taskbar icon that displays the DW editor window and background activities window, then mouse-over on the background activities window beings the hidden overwrite and lose changes to the forefront.  Even though it is visable one can not interact with the dialog box as its non-modal and all of DW is frozen waiting for user interaction with a hidden dialog box.
If you read the posts - the common problem is that FTP connects properly intermittently, results in long waits/timeouts.  FTP cant publish when the preceding FTP is hung-up. Forcing a cancel often frees up the blockage allowing FTP to post properly / maybe on the following attempt.  While this is part of the problem, its not the entire problem.  If one is a web developer working on multiple sites and makes updates often, this problem is very pronounced. Switching between websites is also a problem and causes DW to greyout and the system to respond that the Dreamweaver application is not responsive close or wait....   I wait and it comes back.  I am on an I7, Win7 Pro, All SSD drives - my PC smokes.  However, DW has issues related to bottlenecking or waiting for some internal process to respond before allowing FTP or a change from one local site to another.  - If the FTP is not locked up, I can open and close different sites as fast as I can click.  FTP upload site-A and then switch to site-B, DW hangs up, does not release Site-A (for a while) and the OS pops up a dialog that the application is not responding.   
Instead of  guessing at problems, Adobe should create web space on Linux and Windows platforms, load a test site that is comparable to a real world site with linked CSS, included images, .... and then do some posting and analyze the problem first had. Adobe has the resources to test its code.  If Adobe needs access to a live case, I will provide access.  You have my profile information, call or email me and I will respond.