Cliff Bowman wrote:

> 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).

Ummmm. Gee. Guess what. That's one of the main design issues. In fact my first
little tests have a "User" transport that has you pick a text file on your
system with the job description. Then if you are missing assets, it gives you a
text snippet to send as a request to the server. I also had a basic mail one so
that it would automatically mail the requests via SMTP.

For the IMP, the use case is that Internet traffic time is in short bursts, and
render times take quite a while. Disconnected rendering is a must.

At the moment I'm working on the HTTP stuff. Another test version should be
viable any day now. In theory you could even use a simple static page HTTP
server to feed a local turtle ranch.

> 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!

--
"My new computer's got the clocks, it rocks
But it was obsolete before I opened the box" - W.A.Y.

Post a reply to this message