Re: Distributed testing idea

[Ken Williams]

Some thoughts:

1) In order to be convenient for the code author, he/she should be able 
to poll for available clients before submitting a job.  My inclination 
would be to make this a simple inetd on the client, rather than any 
persistent connection between client & server.  I think if there were 
daemons on the client, or if the client had to connect to a daemon on 
the server, lots of clients would forget to do it when they rebooted.

2) I'd be very hesitant to let anyone do this on my machine.  I don't 
worry [much] about malicious code, but when I'm testing 
non-ready-for-CPAN code, I have done some pretty dumb things.  At the 
very least, I'd create a new user account for the testing processes and 
give it very low priorities.  I also think I'd want to set it up so 
that I only give access to certain code authors, and they *MUST* be 
properly signed with a SIGNATURE file.

3) I'd sure be interested in it for Module::Build.

 -Ken