Can WebDAV be the new Dokan ?

Mar 1, 2011 at 2:26 PM

Placeholder for the useful stuff I'm thinking of doing:

Mar 1, 2011 at 2:47 PM
Edited Mar 1, 2011 at 8:05 PM

Slow Windows WEBDav.. See the following for Tips for each OS and how to speed them up.

or use a differnt client like TotalCommander and the WebDav plugin

Mar 1, 2011 at 5:24 PM

Probably the best feature set for a "Free" Web Cient

Also does drive mapping and explorer integration as well :-)

Mar 1, 2011 at 6:17 PM

Standalone c# Servers

C# WebServer



Mar 1, 2011 at 9:35 PM

I don't know I think webdav has to hide it very well that it is webdav to be considered an alternative to a high-layer but low-level platform to establish what we are trying to establish on...

Also WevDav is not the greatest performance-wise...


Mar 2, 2011 at 6:08 AM
NLS wrote:
Also WevDav is not the greatest performance-wise...

You keep saying that, And I agree that the initial default implementation from MS was not good (Upto IIS 6.0); But, so far my reading on the subject has given me the following plus points

  • The cliet delays can be removed with a simple registry mod
  • The IIS WebDav can be modified to allow greater throughput
  • IIS 7+ has native class 1 .Net plugins so allows greater flexibility
  • The Client side has been replaced by several free clients that allow FTP speed throughput
  • It could give a consistent interface to local and remote users (i.e. removes the difficulties I'm having with identify the attach point)
  • WebDav# is a project that allows the protocol to be "Hidden" inside another application / service
  • It allows native Windows ACL's and security
  • It could allow "Cloud like" access to the Home storage
Mar 2, 2011 at 8:13 AM

Undoubtedly it has benefits, but the only thing to convince me that it would be the same speed as a filesystem driver is to see it working. :)

In any case even if it does have some performance issues, if it can stream a 1080p stream without breakups it will be ok I think.

Mar 24, 2011 at 9:07 PM uses Dokan to allow drives to be mapped to remote ftp services.
So that's okay, As I have that functionality working as well.. It;s just then making this (Liquesce) work over a share that all falls flat !
So how about an FTP Service and then either Explorer [Win 7 instructions near the bottom] (May be Slow as it only uses 4096K buffers) or Netdrive (Free for Home use) to perform the share attach. Would that alleviate the speed fears of WebDav ?

A Question:
Does WebDav and / or FTP support explorer's need to only open the first x number of bytes (to determine the file type / version / Icon location etc.)?