aboutsummaryrefslogtreecommitdiffstats
path: root/lib/kernel/test/pdict_SUITE.erl
diff options
context:
space:
mode:
authorUlf Wiger <[email protected]>2011-01-17 15:47:00 +0100
committerHenrik Nord <[email protected]>2011-11-24 09:36:13 +0100
commitb0426732cc19598f0c0c310b1e79918252495259 (patch)
tree1df6738bed330f1db2f5cde963d153978b867378 /lib/kernel/test/pdict_SUITE.erl
parentf545894e96d5898285eee8dce812c885cf208fb7 (diff)
downloadotp-b0426732cc19598f0c0c310b1e79918252495259.tar.gz
otp-b0426732cc19598f0c0c310b1e79918252495259.tar.bz2
otp-b0426732cc19598f0c0c310b1e79918252495259.zip
Add plugin support for alternative name lookup
OTP behaviour instances (gen_server, gen_fsm, gen_event) can currently register themselves either locally or globally, and the behaviour libraries (including gen.erl) support both addressing methods, as well as the normal Pid and {Name, Node}. However, there are alternative registry implementations - e.g. gproc - and one can well imagine other ways of locating a behaviour instance, e.g. on a node connected only via a TCP tunnel, rather than via Distributed Erlang. In all these cases, one needs to write extra code to identify the behaviour instance, even though the instance itself need not be aware of how it is located. This patch introduces a new way of locating a behaviour instance: {via, Module, Name}. Module is expected to export a subset of the functions in global.erl, namely: register_name(Name, Pid) -> yes | no whereis_name(Name) -> pid() | undefined unregister_name(Name) -> ok send(Name, Msg) -> Pid Semantics are expected to be the same as for global.erl This can be used in all places where {global, Name} is accepted. faulty export in gen_fsm_SUITE.erl await process death in dummy_via:reset() fix error in gen_[server|fsm]:enter_loop() fix documentation
Diffstat (limited to 'lib/kernel/test/pdict_SUITE.erl')
0 files changed, 0 insertions, 0 deletions