That's the point, isn't it. All my webdav files here are www-data: and [d]rw[x]------. Everything above this level must be handled by Apache or Samba, to my understanding.
Yes, to a point. I guess I should have been specific, the user that originally
loads Samba does not need to be the same as the apache user. This would not solve anything. Samba users (the *nix users that actually access the shares) and apache being the same users would sove the issue. A big problem though, it's difficult to have apache spit out sever child daemons as different users, especially if there's several users.
So you've got everything you need?
I've got a workaround for now with the permission issue. I also understand changing the default group for user httpd, it still didn't work for me. Apache would still only write as the group in httpd.conf. So if I want httpd to belong to group httpd and hdusers, and write files to the shares under "hdusers", but have apache run under group "httpd", still doesn't work. The only way I got things to work was to set Apache to run as group-hdusers in httpd.conf. This is definately not ideal, so I wouldn't call this issue completely fixed.
The locking issue, I am still looking into where samba's lock dir is and am goring to experiment with coding a few things from there. So, the locking issue, though to a huge problem, is also not fixed, rather not fixed at all yet.