Re: Scheduling tasks the _hard

What about having your script set an 'at' job that will run it again in 1 minute (or whatever)? Or, if you have to trigger it via HTTP from your office at least use the scheduling on your office computer to run a script that sends the HTTP message. Relying on a web browser to stay up and keep refreshing a page is crazy.

Comment on Re: Scheduling tasks the _hard_ way

Replies are listed 'Best First'.
Re: Re: Scheduling tasks the _hard_ way by Yukio (Sexton) on Oct 17, 2001 at 01:22 UTC
The 'at' is an excellent suggestion. It will mean though I will have to write a VBScript or WScript program to emulate a browser hitting the secure server (and I'm not even sure they can initiate HTTPS connections). I'll start looking in to that. It's a great idea. I also agree with you that depending on a webpage is crazy. It's unfortunately a sign of my desperation.	[reply]
Re: Re: Re: Scheduling tasks the _hard_ way by perrin (Chancellor) on Oct 17, 2001 at 01:37 UTC
I'm sure VB can load a web page, but Perl can too. You could install perl on that office machine and use LWP to do the HTTPS request. It may be harder to get SSL working that way though, than to simply use the VB stuff (which I think runs the IE code to do it).	[reply]