An excellent resource on internal BeOS mechanisms from an engineering perspective is available in the old BeNewsLetters. An archieve is kept at several addresses, I've been using this one recently ( http://testou.free.fr/www.beatjapan.org/mirror/www.be.com/aboutbe/benewsletter/article_index.html). If you wish, you can also search by date index ( http://testou.free.fr/www.beatjapan.org/mirror/www.be.com/aboutbe/benewsletter/index.html). There are also links to older newsletters going back to 1995. Be prepared to say goodbye to the rest of your weekend... On Sun, Oct 4, 2009 at 7:55 AM, Stephan Assmus <superstippi@xxxxxx> wrote: > Hi, > > On 2009-10-03 at 21:44:48 [+0200], Alexandre Moreira > <alexandream@xxxxxxxxx> wrote: > > Hello, everyone. I've been trying to understand the way BMessages work in > > Haiku/BeOS, but I'm having some trouble. > > > > Can anyone please explain a little about how BMessages compares to > > DBus-Style messages, so I can leverage previous knowledge to better > > understand them? > > A great overview is in the BeBook: > > < > http://www.haiku-os.org/legacy-docs/bebook/TheApplicationKit_Messaging.html > > > > In a nutshell: BMessage is a container that can hold typed data, arrays of > data and also other BMessages (nesting). It also offers utility methods for > getting info about the sender of the message and how to reply. Messaging > works either by attaching messages to the message queue of a BLooper, if it > is part of the same process, or by flattening it and transmitting it via a > port (a kernel feature somewhat similar to pipes). The receiving BLooper > lets the target BHandler process the message, a BLooper is also a BHandler > and is the default handler. I can't really say how this compares to DBus, > since I don't know anything about it. Since BMessage passing was > fundamental to BeOS, the BeBook explains this really well, so you should be > able to learn everything about it from the above link and the other > chapters. > > Best regards, > -Stephan > >