Trace SharePoint Designer
Interesting problem with WebDav calls not working because IIS7 had web dav publishing enabled.
GetUsage BLOB RPC call.
(1) Copy.asmx file upload.
Byte array can have contiguous memory allocation problems on the server.
(2) WebDav (WebClient) file upload
No metadata can be uploaded.
(3) RPC (FrontPage) file upload
However, it does not support sending any metadata long with the file content. This can be a major problem if the document library has multiple content types, so the new file will be put into the document library with the default content type. Another big issue is if the default content type has required fields. The file will remain checked out until the fields are populated. This prevents other users from seeing the document or from being returned in any searches. It is a great solution if you are just bulk migrating data from an external data store to SharePoint. You more than likely will have to do extra work afterwards. Adding metadata after uploading will also cause the creation of extra versions of the document being created unnecessarily. The fact that it does not use the soap protocol but straight http makes it more scalable than the copy web service. Unfortunately, it still suffers from the fact that it uses a byte array to upload the file. So sooner or later you will run into “out of memory “ exceptions. So how can I create a folder before using WebDav? You can use the lists web service to accomplish this: