G
gvtsstaggs
Guest
I'm just a lowly developer, but one that happens to have experience with both progress and erlang (as well as elixir), having written a couple of applications in both languages (they both compile down to erlang byte code). I agree with gus that the Actor model of concurrency is the way to go (it's a trade-off between memory usage and the need to use locks). But, when concerning screen/database changes for a particular program, would it make sense to have a single thread for both, and anytime a screen change or database access/change takes place it sends a message to that particular process? I know that with Erlang, opening a file returns a process id for which you can send messages to. If you pass around this process id to other processes, you effectively have concurrent access to any particular file. Just thoughts to add to the discussion. Solomon Staggs
Continue reading...
Continue reading...