Usually software optimized for single-computer multiprocessor threads, which is definitely different than using processes. Windows systems are very usually based on threading, instead of multiprocessing, which is popular on unix (because of large mainframes with memory on processor board).
Threading software which uses memory to share data between threads does not work well in a distributed environment.
If the software started every filter as it's own process, and piped their output (extend your definition of pipe if multiple input/output pipes with timecodes seem complicated), the OS could easily make a distribution plan on the fly when it noticed that processor is getting overloaded.
Slashdot Mirror
actually not a bad idea. i've been thinking of a high-tech "outlaw" colony for a while, but unfortunately they would come after us.. with a railgun.
.. noo, they're too religious, in the bad sense of the word.
maybe we should join osama's forces?
now you're missing the difference between ozone layer and greenhouse effect. heat not escaping earth does not cause skin cancer.
:)
but good point about this byreauc.. democracy we have these days.
Usually software optimized for single-computer multiprocessor threads, which is definitely different than using processes. Windows systems are very usually based on threading, instead of multiprocessing, which is popular on unix (because of large mainframes with memory on processor board). Threading software which uses memory to share data between threads does not work well in a distributed environment. If the software started every filter as it's own process, and piped their output (extend your definition of pipe if multiple input/output pipes with timecodes seem complicated), the OS could easily make a distribution plan on the fly when it noticed that processor is getting overloaded.
there already is gnutella, and that is open source. (plus it cannot be shut down) ((plus it can also trade movies and games))