"Stefano Ceccherini" <stefano.ceccherini@xxxxxxxxx> wrote: > 2008/1/4, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>: > > The documentation in the BeBook is more helpful here: if you pass > > in a > > reply message, the call will be synchronous, if not, it's > > asynchronous > > (regardless of wether or not you specify a reply target). > Ok thank you. Another question. > Could be that our BLooper::PostMessage() deadlocks in case the > message > queue is full ? At least, switching to BMessenger::SendMessage() > fixed > a deadlock I had in my code, and examining the backtrace I noticed > that the app was locked in PostMessage(). There are two reasons why this shouldn't happen: 1) our PostMessage() just uses SendMessage() 2) our SendMessage() just moves the message into the internal looper queue regardless of the port queue So if your app was locked in PostMessage(), it should have been another reason - but it would still be nice to know which one that was :-) Bye, Axel.