in reply to Re^2: Socket or not
in thread Socket or not
Sorry to waist your time.
You didn't waste my time. I was attempting to avoid wasting yours.
Programming, setting up, and maintaining, all the code, logistics and required security that sit behind your desired: "I wanted to make a batch file or a perl script that they could simply double click to run the conversion. " is a very involved process that would require you to learn substantially more about programming that you currently know.
And the main point is, what you want is actually quite easy to setup, quickly & securely, using the existing facilities of your OS. But programming it in Perl will require considerable effort.
If you are considering doing it in Perl in order to bypass some political barriers, then you should really think twice 10 times before going ahead.
Because, if by doing this, you are crossing some "political" boundaries, then it could very well end up being detrimental to your source of income and career. Especially if you get the hardest aspect of the task--security--wrong.
If you really insist on going ahead, then the simplest mechanism would be to create two directories below the current shared directory--say \\yourWorkstation\sharedspace\IN & \\yourWorkstation\sharedspace\OUT--and then you run--once at the beginning of each day or week--a simply script that monitors the IN directory, when it sees a file appear there, it runs the conversion process and writes the results to the OUT directory.
Now all your users have to do is upload the files to the IN directory, and then check the OUT directory to see when the converted files are ready.
But even this is not entirely trivial as your program will need to to not only detect when the files appear in the IN directory, but also wait until their upload is complete before starting to process them.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^4: Socket or not
by ahmad (Hermit) on Nov 25, 2010 at 02:45 UTC | |
by BrowserUk (Patriarch) on Nov 25, 2010 at 02:52 UTC |