blocking communication?

Hi!

I am a PhD student of the TU-Vienna. I followed the last discussion about
communication and configuration (states, interupts, ...) with high
attention. For me a simple question arises:
Why do you use blocking communication patterns? 
My answer:
1) I know that design and implementation of non-blocking communication
produces a bit more effort.
2) But permitting only non-blocking communication can avoid the dangerous
situation of reciprocative blocking and hence deadlocks. 

Isn't it better to use only non-blocking communication, because it enables a
seperation of communication and configuration?
(Seperation of communication and configuration = allows using differnet
tools, seperated development, ....)

regards

Wolfgang 


-----------------------------------------------------------
Dipl.-Ing. Wolfgang Ponweiser
Institute of Flexible Automation
Vienna University of Technology
phone: +43/1/504 14 46 - 14 | fax: +43/1/58801-36199
web: www.infa.tuwien.ac.at    | email: [email protected]