A couple of questions, Howard
I'm working on updating dfQ so that it will work for Phase II, and I've got a couple of questions. As a reminder dfQ is primarily intended for no-netting. That is it automates the uploading process from clients that have no internet access (but are (indirectly) connected to another computer which does).
Here's where the question I posed to you a while back about separating the functionality of listing files to upload and saving extra information, instead of saving it all in filelist.txt has come back to haunt me, I think.
Specifically in terms of uploading files. Traditionally, it's been ok to go ahead and upload the .val and .log files along with the filelist.txt. In terms of the behavior on the client, all of these files could be transferred together to another computer and uploaded from there. Once the files have been copied to another location it's ok to delete all of them.
Under the new phase, the filelist.txt contains the file list and extra info. Thus filelist.txt cannot be deleted on the client side. Is it ok to delete the .log and .val files and to leave an erroneous filelist.txt file behind? It is erroneous because it lists files for upload which are no longer present in the current directory. If I don't delete the .log and .val files then the amount of traffic will keep on growing and growing.
Please respond as soon as you can since there are quite a few computers out there (hiya djp) running dfQ and I'd like to offer them as seamless a transition to Phase II that I can.