🚀 go-pugleaf

>>Have you tried writing something in CCS or CSP, which are based
>>on synchronous communications?  It seems quite natural to me.

>.  I think modeling client/server "synchrony" and "asynchrony"
>in CCS or CSP would involve modeling the communication media as a
>separate process, which would lose you a lot of the benefits of CCS and
>CSP's "synchronous" communication.

CSP/CCS programming is natural to the degree to which it hides asynchrony.
To model almost any interesting communications in CCS you have to model 
the channel/medium/etc as a process. Otherwise it's just not flexible enough.

For client/server models, you would might model each transaction as a port
(think of the transaction ID) and attempt to synchronize with it, or you
might assume all transactions are synchronopus server calls and try to
synchronize with the server.

Generally I find it easier to deal with asynchronously executed sets of 
synchronous tasks. Procedure call is just ingrained in most programming
languages. Asynchrony introduces too many intermediare/indeterminate states.

By the way, is the asynchronous logic stuff still going?