Posted by Marc Shevick on September 04, 2012 at 10:48:55:
As mentioned in previous emails, I have a client that still experiences problems when doing copyfiles from the comet anywhere host to the local machine. The problem is NOT a comet issue and then client is still troubleshooting this part of it. Unfortunately, the result is that when the copyfiles take place, it creates a read only file with 0 bytes. And subsequent copyfiles with duplicate file names do not take place even with the overwrite flag set. Even the process of restarting the comet anywhere session which should reset the TMP directory on the local machine will still leaves these files in the folder. Unless I log into the local machine and manually delete these files, the process can not continue. Is there anything that comet can do to delete a read only file? I guess I know what the answer will be, but I promised the client I would ask.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.