XPost: alt.comp.os.windows-11, alt.comp.os.windows-10   
   From: mariasophia@comprehension.com   
      
   This is intended to be a formal team discussion of the topic:   
     FTP vs WebDav for Android/iOS filesystem sharing on Windows PC   
      
   This thread is intended to summarize & then discuss the practical   
   differences between FTP and WebDAV for Android or iOS filesystem sharing on   
   a Windows PC.   
    Protocol   Network Location   Drive Letter   Native   Needs 3rd Party   
    FTP        Yes                No             Yes      Yes   
    WebDAV     Yes                Yes            Yes      No   
      
   The goal is to clarify what Windows can do natively, versus what requires   
   third-party tools, and what the terms share, mount, network drive, and   
   network location actually mean (since Windows terminology is confusing).   
      
   IMHO:   
   1. FTP is simple. So is WebDAV.  On Windows. On Android.   
   2. Both are native to Windows. Both have free servers on Android.   
   3. There's no difference in simplicity between them (as far as I can tell).   
      
   FTP:   
   A. FTP is fine for ad-hoc file transfers.   
   B. But FTP cannot provide a native drive letter on Windows.   
   C. FTP requires third-party tools for filesystem integration.   
      
   WebDAV:   
   a. WebDAV provides native drive-letter mounting on Windows.   
   b. WebDAV integrates cleanly with Windows scripts, applications & tools.   
   c. For full filesystem interoperability between Android or iOS and Windows,   
      WebDAV is more capable than FTP if mapping a drive is one of your needs.   
      
   Occam's Razor says a simple solution that solves all needs is likely best.   
      
   FTP ON WINDOWS   
      
   1. Windows includes a native FTP client, but it does not include an FTP   
      filesystem redirector.   
      
   2. Because there is no redirector, Windows cannot mount an FTP server as a   
      drive letter.   
      
   3. Windows Explorer can open an FTP server as a virtual folder.   
      This is called a Network Location, not a Network Drive.   
      
   4. Example of a Network Location:   
        C:\> explorer.exe ftp://username:password@host/   
      
   5. This is not a mount. It does not create a drive letter.   
      It does not behave like a filesystem.   
      It is only Explorer acting as an FTP client.   
      
   6. To get a real drive letter for FTP, a third-party redirector   
      is required.   
      
   7. Example of a third-party mount:   
        C:\> ftpuse Z: ftp://192.168.1.2 user password   
      
   8. This works apparently, but it is not native Windows functionality.   
      
   WEBDAV ON WINDOWS   
      
   1. Windows includes a native WebDAV filesystem redirector called WebClient.   
      
   2. Because the redirector is built in, Windows can mount WebDAV as a real   
      network drive with a drive letter.   
      
   3. No third-party tools are required.   
      
   4. Example of a native WebDAV mount:   
       C:\> net use Z: \\192.168.1.2@8000\DavWWWRoot /USER:jim * /PERSISTENT:YES   
      
   5. DavWWWRoot is a Windows native keyword that has existed since the days   
      of Windows XP and Windows Server 2003.   
      
   6. This is a mapped network drive, not just a network location.   
      
   ROLES: SHARE VS MOUNT   
    a. A server shares a filesystem.   
    b. A client mounts a filesystem.   
    c. FTP servers on Android can share, but they cannot mount anything.   
    d. WebDAV servers on Android can share & Windows can mount them natively.   
      
   Occam's Razor:   
      
    i. The simplest solution is not what makes any solution likely the best.   
    ii. The best solution is usually the simplest one that solves all needs.   
      
   Certainly FTP is simple, but FTP is limited.   
   FTP cannot provide a drive letter without third-party Windows tools.   
      
   Just as certainly, WebDAV is simple too. Just as simple as FTP is, IMHO.   
   And WebDAV provides native drive-letter mounting on Windows.   
      
   WebDAV solves more requirements than FTP in a Windows environment.   
   If you don't need or want native drive-letter mapping, then FTP is fine.   
      
   But they're not equivalent.   
    I. FTP is less functional in that respect than WebDav is.   
    II. Yet, both are super simple.   
      
   KEY QUESTION FOR THIS TEAM DISCUSSION   
      
    Q: What does FTP do better than WebDAV for Android or iOS filesystem   
       interoperability on a Windows PC on a local LAN?   
      
    A: ?   
   --   
   Usenet is a forum for discussing essential tools we use to solve problems.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)