April 16th, 2003

sleepy

(no subject)

You know, sometimes you can expose some truly atrocious programming practices by browsing through what system calls are being made.

Take, as example, the folding@home distributed computing client. As it's running, it spawns the core seperately - okay, no prob with that. However, it also wants to display the core's output in its status window. So, who can give me a good suggestion for getting this to happen?

Did anyone say "have the core write a log file, then read the log file several times a second to see if more data has been appended on the end, then display it, even if the client in running in service mode and therefore 'displaying' the data is utterly futile since nobody will ever see it?"

Because if you did, you should go write some code for the folding@home distributed computing client. You'd fit right in.
  • Current Mood
    irritated irritated
sleepy

(no subject)

Success:

When your new server has detected a new job, started it, finished it, and done the cleanup before the old server has even noticed it.
  • Current Mood
    accomplished accomplished