Communicating between two computers

[Dale Strickland-Clark]

Start simple.

Unless this is particularly time critical, I'd create a folder on the Build
server  and share it with suitably limited access.

Give the Web server write access to the folder.

The Web server writes a batch file or Python script to the shared directory.

Every few minutes the Build server checks this folder for a file and
executes it.

If you need some feedback, it could change the name of the file or move it
to a subdirectory while it's running so the Web server can see it's active.

--
Dale Strickland-Clark
Out-Think Ltd, UK
Business Technology Consultants

donotspam-jen at personic.com <dnotspam-jen at personic.com> wrote in message
news:395d48b3$0$21842 at wodc7nh0.news.uu.net...
> FYI, I'm doing all of this on Windows NT, in case that makes a difference
> ...
>
> Is there a good way to get a script on one computer to talk to a script on
> another computer?  The process I'm thinking of is pretty simple ... I want
a
> script on a Web server to be able to send a command to a build server to
> start a build process.  I'd also like the Web server to be able to query
the
> build servers to find out their status (so that two builds do not run at
> once on the same machine, for example).
>
> I've read a little about SOAP, but I think that my needs are probably a
lot
> simpler than that.  The easiest way to accomplish this is to setup a Web
> server on each of the build machines, too, I guess ... but I was hoping
that
> I could just have the scripts that run on the build servers run as NT
> services.
>
> Thanks!
>
> Jen
>
>
>
>