Tue Dec 20 09:15:15 CET 2005
Robert Raschke writes:
> If your application uses ets as a communication mechanism between
> processes, that is surely quite a sore design mistake.
Looking at a freshly started erlang node, I can see a number of ETS
In some (many? most?) cases, ETS seems to have been used for no
particularly good reason at all. For example: inet_db is a gen_server
which uses an ets table (inet_db) to store its 20
The only explanation I can think of is "it must be historical
junk". Or am I missing something?
More information about the erlang-questions