APM: fork on windows / long-running process and cgi

Sam Foster austin.pm at sam-i-am.com
Fri Feb 9 11:21:21 PST 2007


> "Micro-optimizations yield micro-results."  You will do builds what,
> several times a day, and check their statuses a few dozen times a day?
> Unless fork() simply didn't work (and it does work, in my experience
> with Cygwin's perl at least), I don't see why you'd bother to avoid
> it.  Am I missing something?
>
>   
I had made a first pass at this and ran into problems which seemed to 
center right around where my script was supposed to be forking. Rather 
than bang my head against it I thought I'd check if this is even 
supposed to work, or what other options there are. Taylor is right 
though that I really dont need a fork, I just need to kick off the 
process, hang up with a response (I just close stdout right?) and let a 
future request check on the status. I'm already persisting some info 
about the build to a file so I could add build status in there.

Tim: all you are missing is that in truth I dont know what I'm doing, so 
my uncertainty is not about optimization, more about learning good 
patterns that will serve me in the future.

Sam


More information about the Austin mailing list