Re: distributed processing ad multiThreading
Re: distributed processing ad multiThreading
- Subject: Re: distributed processing ad multiThreading
- From: Drew McCormack <email@hidden>
- Date: Mon, 17 Sep 2001 14:59:38 +0200
This approach assumes no communication between the nodes, with each
running independently.
No, each process can still communicate with every other process, though
they do run relatively independently. Communication is via function
calls made from each node.
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.
I kind of doubt you can do it without a 'server' running on each of the
machines. In other words, i suspect you would need to have some sort of
program running on each machine, whether or not it is your main program.
Anyway, have you checked out the cocoa documentation for distant objects
(eg NSDistantObject)? This sounds like what you want. Although i think
you will still need to have something running on each machine to begin
with, in order that the master node can make a connection.
Drew McCormack
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
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev