On Thu, 12 Aug 1999 07:58:04 -0700, "Jon A. Cruz"
<jon### [at] geocitiescom> wrote:
[snip]
>In general, there will be a set of renders in the queue. Clients will ask
>for the next render, and will get them in turn. Needed assets (includes,
>textures, etc.) will only be sent to the client if they do not already have
>it (reduces network traffic). Once the image(s) are done, they are packaged
>up and sent back to the specified location. So it is one render per client
>computer. 

Certainly sounds interesting - and I've a small render farm to test it
on. Actually more like a tortoise cage in the back garden than a farm,
but you get my drift I'm sure.

One thing that'd be interesting (or not) would be a LAN farm with
occasional WAN clients - maybe with HTTP/FTP communication on the LAN
but requests and results via e-mail to "the outside world" (it's
prohibitively expensive in the UK to remain online for any large
amount of time).

It's be nice to know how much work is required at the server end
(setting up dependancies and the like) but... well, I guess I'll have
to go take a peek at your early documentation!


Cheers,

Cliff Bowman
Why not pay my 3D Dr Who site a visit at http://www.who3d.cwc.net/
PS change ".duffcom" to ".net" if replying via e-mail

Post a reply to this message