[erlang-questions] every process should have a URL

Oliver Korpilla <>
Fri Sep 16 09:38:57 CEST 2016

Hello, Joe.

Couldn't this be easily spoofed? (by setting IP, hostname, nodename accordingly or man-in-the-middles etc)

Also, what is the value of "local PID in node" when the basic assumption of Erlang is that a process is restarted on crash and replaced by an equivalent one? (which would have a different PID)

If Erlang would replace crashed processes with processes or identical PID (and one wonders how, really) then the "local PID in node" might be interesting... else something else would seem more sensible (to me). 

Couldn't an Erlang node run a registry for this for every process that "wants" the overhead of having a global name? The process then could give it an ID it wants to assume just as with gproc etc. Global requests could query that registry. Spoofing problems remain, I guess, on various levels.


Gesendet: Freitag, 16. September 2016 um 09:16 Uhr
Von: "Joe Armstrong" <>
An: Erlang <>
Betreff: [erlang-questions] every process should have a URL
Alan Kay at 43 min and 21 seconds into his OOPSLA 1997 (the computer
revolution hasn't happened)

Says: "Every Object should have a URL"

The video is here:


The Objects that Alan talks about seem to me to be very like Erlang
processes - understand polymorphic messages - have late binding etc.

So how can we make truly global Pids? - global meaning an address space
consisting of every machine on the planet running BEAM code.

If we did this programs to do chat/email/instant messaging/.... etc
would be trivial to write.

What would a Pid look like - a
{HostIP,PortNumber,NodeName,LocalPidinNode} tuple?


erlang-questions mailing list


More information about the erlang-questions mailing list