Path: utzoo!utgpu!attcan!uunet!husc6!mailrus!cornell!batcomputer!itsgw!leah!rds95
From: rds95@leah.Albany.Edu (Robert Seals)
Newsgroups: comp.misc
Subject: Re: Worm CPU usage.
Summary: YES YES YES
Message-ID: <1233@leah.Albany.Edu>
Date: 10 Nov 88 12:53:04 GMT
References: <7600@well.UUCP>
Organization: The University at Albany, Computer Services Center
Lines: 16

In article <7600@well.UUCP>, pokey@well.UUCP (Jef Poskanzer) writes:
> Now, if we could harness that kind of power for useful work...  Imagine
> a net-wide distributed ray-tracing service.  If you want something traced,
> you send the NFF to a central clearinghouse.  All over the net, people
> start ray tracing servers when they leave for the day.  These servers
> connect up to the clearinghouse and fetch the scene description, and a
> list of pixels to trace.  By morning, hundreds of scenes have been traced
> and returned to their senders.  (Close your mouth, you're drooling.)

I guess most of us [well, at least the groovier of us, anyway...] have
thought about this. Do we all need RPC? Why aren't we doing it now? They
do it at CMU, and apparently at DEC and elsewhere, so why not 'distributed
ray-tracing (or luminace modelling, or acid deposition modelling, or...)
for the rest of us'? I'd contribute my meager resources each night...

honest, rob