Tue Dec 20 20:38:08 CET 2005
Robert>>> If your application uses ets as a communication mechanism
Robert>>> between processes, that is surely quite a sore design mistake.
Ulf> Note the wording "ets as a communication mechanism"
> I have a fair idea of what most of these do, and
> I don't think any of them use ets as a communication
> mechanism, but rather as an internal storage structure.
You're most likely correct: it doesn't quite fit Robbie's description.
But it's just as pretty: an "internal storage structure" which
happens to be publically writeable and named, just ready for someone
to, um, communicate with it.
More information about the erlang-questions