Re: distributed processing ad multiThreading
Re: distributed processing ad multiThreading
- Subject: Re: distributed processing ad multiThreading
- From: Robert S Goldsmith <email@hidden>
- Date: Mon, 17 Sep 2001 13:37:56 +0100
Hi :)
Even if you decide not to go with one of these standard solutions, you
would probably still end up doing something similar, ie, starting a
separate copy of the program on each node, using UNIX, and having them
communicate by whatever means you decide upon. In this approach, you
wouldn't actually need to use NSThread or something equivalent, because
you simply start a separate copy of the program running on each machine;
each copy is really a separate thread.
This approach assumes no communication between the nodes,
with each running independently. Although each node of my
system would run for up to a second at a time
asynchronously, there are synchronization points and quite a
lot of communication between the threads / processes. Also,
it would be better to have the controlling application
allocate which machine which entity exists on so I don't
have to manually run each app or get a shell script to do
it. It would be best simply to write a system that takes a
file of ip addresses, checks the load on the machines and
distributes n processes over m machines where n >= m.
Of course, it would be best to make this all as transparent
to the actual core code as possible so the actual objects
don't know or care where they are running.
I know objective c has systems much like this and was hoping
to expand on them to achieve my needs. The objects are
objective C anyway because each entity is easiest to program
using dynamic binding.
Robert