Dear Enrico,
It looks to me that message passing is the paradigm of choice, since
processing one lookup might involve non-trivial state updates. Message
passing allows you to process one request at a time, and therefore
serializes all requests to the dictionary.
By the way, I don't really understand the second requirement you stated.
What are the feedback and the equilibrium?
Cheers,
raph
Enrico Santoemma wrote:
Hi,
the question is about which paradigm is better in implementing this
object: declarative concurrency or message passing concurrency, or
perhaps some other way.
These are some requirements:
- should map keys to values
- a key lookup should find values which are then fed into the
dictionary _ a kind of feedback _ until an equilibrium is reached
- a key lookup also modifies the object's internal store
I guess message passing is needed, because this design has intrinsic
non-determinism and race conditions are welcome. I wonder if there are
other paradigms which are better, before start coding.
Thanks,
Enrico
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
