in reply to cgi file upload without a form

Underspecified. Ambiguous.
  1. "to enter a directory" - a directory WHERE? On the server? on the client?
  2. "I know which files..." - oh, how?
  3. "... to upload" - errrrm... transfer from the server to the client, or the otherway around?

This makes sense to me only if you have hardcoded files to download from the server to the client, based on the user's selection of a directory (from a menu? psychic choice?) in which case, this seems to be a case of needlessly going all around Robin Hood's barn. Wouldn't it be more direct to render, as a list of options, the files available to download with explanations of their relevance, utility or some other descriptive language?

And...
What have you tried? WHere's the code?

Replies are listed 'Best First'.
Re^2: cgi file upload without a form
by raybies (Chaplain) on Jan 13, 2011 at 19:32 UTC
    C'mon. Have a heart. Have you considered? Maybe he's trying to create spyware or some virus software? :)
      Sorry.

      Admission to the SpyWare Makers' Guild requires some evidence of aptitude. The Virus Writers Conglomerate has a somewhat similar pre-req: demonstrated competence in producing some form of malware.

      :-)
      I can assure you this isn't spyware. Basically this is my scenario. We have a set of test results with static names that get written to a new directory after every test run. After the test run we need the ability to point at a specified directory and upload the required files...like I said we know which ones we need. The way I'm currently doing it is uploading one file at a time. This is not only time consuming but makes it easy to make a mistake.
      Any thoughts?
        Solution #1. Make the last step of the test run be to make a tar file with a specified set of files in it. Then upload that tar file, and on the other end untar it and extract the files you need.

        Solution #2. Write a script that runs on the client that uses the LWP library to upload the selected files one by one.

        Solution #3. Find a different way to move the files. Perhaps using a shared filesystem.