Linc - Thanks for the response. However, if my local machine is smart enough to recognize that it is trying to copy .DS_Store on top of a preexisting .DS_Store, good behavior would be to skip that one file and continue copying. At the end of the copy process, the OS could report that files x,y, and z failed to copy.
Bad behavior is for the operating system to simply abort midway through the copy process. If I'm copying 15-20,000 files in hundreds of folders, each with sub folders, (which I do often) it is a real PITA to figure out what has copied and what hasn't. It is ESPECIALLY bad behavior when the copy process aborts, and then when I try to simply trash the partial file, the partial file can not be removed from the trash because "a file is in use", and I have to resort to a terminal based nuke ( rm -rf ~/.Trash/* ).
So, although there may be issues with WD file transfer protocol (my NAS), I see no reason my mac can't deal with the problem more gracefully than to simply abort, leaving me a mess to clean up. As a long time software developer, I consider that to be a bug in the OS as well as one in WD's firmware.