Re: What is defensive consistency?

hi,

> http://waterken.sourceforge.net/javadoc/org/ref_send/promise/eventual/Eventual.html

Clueless Newbie here.

Does this line of thinking mean that to be super safe, no object would
ever synchronously call any other? (You'd have to use futures or
something (Eventuals) - couldn't even use e.g. Erlang style message
passing because your plan could get pre-empted by the scheduler to
handle one of the messages you generated, in another process.)

You could call your own instance methods (and hope your code doesn't
have bugs wrt internal plans) but nobody else's? I'm just thinking it
could be hard to know what calls on other instances could screw up
your own plans.

sincerely.