in reply to Socket or not

By far the simplest way to allow remote users to run processes on your server, would be to give them ids on the server.

These IDs can be locked down tight so that they can only see whatever you chose to let them see; and run whatever you choose to let them run.

If they are other windows users on the same LAN/WAN then you only need add their domain IDs to an appropriate group on your server and the job is pretty much done. After all, this is what multi-user OSs are all about. If you don't know how to go about setting up an appropriately locked-down group, consider talking to your local systems administrator.

Alternatively, if the users are getting to your server via the internet; or from machines running other OSs, then perhaps setting up a simple webserver which authenticates the users, and then presents them with a menu of tasks they can run would be your best option.

Please don't be offended, but when you use phrases like "how do I run the socket", it indicates a lack of knowledge on your behalf that means that you trying to replicate even a small part of existing OS or webserver functionality yourself, in Perl, really isn't a good idea.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy

Replies are listed 'Best First'.
Re^2: Socket or not
by patmcl (Novice) on Nov 24, 2010 at 16:29 UTC
    Yes, I know nothing about Sockets. I created a simple socket from examples that I found. It works fine saying hello world. I don’t deal with internet programming, I deal with data, data retention, data manipulation, data collection etc.. The technicians that spend hours transferring the large data files from the secured/isolated remote testing network to the workstation know nothing about logging on remotely. Their managers wont let them spend the time logging on remotely (I gave them simple instruction), it is very political. They have read/write access to the shared link to where they put the data on the workstation. When they were done getting the data to the shared workstation I wanted to make a batch file or a perl script that they could simply double click to run the conversion. They know when the data is available and sometimes the data is needed to be converted asap. I do have scheduled times for data conversion but they sometimes need the data at strange time. Sorry to waist your time.
[reply]
      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.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
[select]

        The IN & OUT shared directories looks a great idea

        And I guess the OP might check for fully uploaded files by requiring an md5 checksum for each uploaded file like 'filename.ext.md5' then all he does it comparing the values before processing.

[reply]

In Section Seekers of Perl Wisdom