in reply to triggering a program in web server

As an addendum to arthas's post, you may also use a cron facility on server A that runs the transfer program every so often (modified so that it tests whether there's something to trasnfer).

Just my 2 cents, -gjb-

Replies are listed 'Best First'.
Re: Re: triggering a program in web server
by l3nz (Friar) on Aug 19, 2003 at 13:23 UTC
    Probably the reason why choosing synchronous execution (script A calls script B) or asynchronous is how much time B takes and how you want to handle B's errors. In a synchronous environment you may report B's error to the user (say, destination server is down) and abort the process. If B is expected to be quite fats (say less than a few seconds) handling B synchronously is probably both easier and sensible. If B runs in 'daemon mode', ie as a daemon or using repeated sleep's, you'll have to handle B's errors anyhow using a log or something.
    My $.02
[reply]

In Section Seekers of Perl Wisdom