Ulf Wiger (AL/EAB)
Wed May 19 12:27:14 CEST 2004
Regarding avoidance of global operations,
you should take a look at global_group.
"The global group function makes it possible to group the nodes in a system into partitions, each partition having its own global name space, refer to global(3). These partitions are called global groups.
The main advantage of dividing systems to global groups is that the background load decreases while the number of nodes to be updated is reduced when manipulating globally registered names."
Not sure if anyone has ever used it. I'd be interested
in hearing feedback on it, if there is such.
> -----Original Message-----
> [mailto:]On Behalf Of Joe Armstrong
> Sent: den 19 maj 2004 11:30
> Subject: Erlang distribution
> I'm trying to change how distributed Erlang works.
> Currently, all nodes in a distributed Erlang system know about all
> other nodes. So for example, if node A knows about B and A knows
> about C then B implicitly knows about C. This does not scale to
> systems of millions of nodes
> What I'd like is the following:
> A should be able to do things on B (spawn processes, etc. )
> and A should be able to do things on C
> I don't want any knowldege of B to leak out to C. I'd also like to
> handle multiple cookies etc. ie the coookies needed to authenticate A
> against B whould be different from the cookies neede to authenticate A
> against C.
> I also don't want any form of global operations on all nodes in
> - has anybody done any work in this direction?
> - is what I want possible without perfoming major
> surgery to
More information about the erlang-questions