From: Jan Hubicka hubicka@horac.ta.jcu.cz
Subject: [9fans] XaoS30 and plan9
Date: Mon, 8 Sep 1997 11:51:53 +0200 [thread overview]
Message-ID: <19970908095153.6Hnhn_xuQKhrbI3uMQp002VHUR300CV0HcJyrbw3jek@z> (raw)
On Sun, Sep 07, 1997 at 03:00:42PM -0500, Brandon Black wrote:
>
>
> For the network stuff... at least on *nix machines you could use the PVM
> libraries... POVRay is built with them to make a distributed version
> called "PVMPOV".
Thanks, I will definitivly take a look at this, but main problem
is that I can't imagine main clauclation loop w/o freqent comunication
between computers. At least each must have complette source image, wich
should involve 1MB or more transfers to each computer per frame
(20 times per second) and thats impossible. So I have to think about
less optimal, but networkable calculation loops.
Honza
>
> Brandon
>
> On Fri, 5 Sep 1997, Jan Hubicka wrote:
>
next reply other threads:[~1997-09-08 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-08 9:51 Jan [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-07 20:00 Brandon
1997-09-05 10:06 Jan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19970908095153.6Hnhn_xuQKhrbI3uMQp002VHUR300CV0HcJyrbw3jek@z \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).