in reply to Passing long argument list to remote script

Using a file can certainly work, but I'd suggest creating a table on the database (e.g. report_queue), and let the web server add reports to the queue, and let the back end server pull off requests and execute them. The advantage is that both machines (presumably) already have access to the database server, so you don't need an additional hole in your firewall for some file sharing scheme. (Though, now that I think of it, you could publish your files in a separate server root, and let the back end server fetch them via http. Just a random thought.)

...roboticus

When your only tool is a hammer, all problems look like your thumb.

  • Comment on Re: Passing long argument list to remote script

Replies are listed 'Best First'.
Re^2: Passing long argument list to remote script
by locked_user sundialsvc4 (Abbot) on Feb 28, 2012 at 20:26 UTC

    /me nods...

    That certainly seems to me to be the most flexible approach, since you can as always be certain that changes to exactly what needs to be run will happen forevermore.   (“The only universal constant is change.”)   Whether you get the list of commands from a database table, or from a file that is supplied separately, you certainly do not want to be confined by the arbitrary size of some command-buffer.