[interfacekit] Re: Anyone working on BMessageQueue

Thanks.  I have made good progress on BMessageQueue.  Check out the 
following document, again comments welcome:

http://www.Windswept-IV.ca/openbeos/BMessageQueueUseCases.html

I am making good progress on the implementation and will start making a 
test program which compares my implementation to Be's just as I did 
with BLocker.

Note, my investigation does reveal some comments being made on 
bedevtalk to be true.  Be does seem to make use of friend classes quite 
a bit internally.  In this case, BMessageQueue is a friend of BMessage 
which allows the BMessageQueue to directly modify private members of 
the BMessage class.  I will take the same approach since I think there 
are good reasons for doing so.  The main reason I think is performance.

On bedevtalk, people are discussing whether to recreate BeOS as is or 
try to improve on some of its faults as the work progresses.  My 
approach for now is to implement what I am seeing.  I will document any 
critiques I have of the implementation as I go along and perhaps we 
will revisit them in the future.  However, I am inclined to believe 
that something like the friendship between BMessageQueue and BMessage 
was done for a good reason and changind the implementation drastically 
until we understand those reasons is foolish.

My main concern though is with the more complex classes.  I think this 
friendship between complex classes like BMessage and BApplication etc 
could make our job of figuring out how this stuff works pretty tricky.  
Will we ever really understand some of the side affects of how a 
particular BApplication member might modify BMessages?

My plan next is get some of this stuff checked into cvs (just got cvs 
to sourceforge working last night) and then to work on BMessageFilter 
or BInvoker.  If anyone is already running with BMessageFilter or 
BInvoker, please let me know.

>>I am looking for another class to tackle.  Anyone already working on 
>>BMessageQueue.  Please let me know ASAP because I plan to start it 
now.  
>>Thanks.
>Not AFAIK. BTW, after a quick scan of your BLocker docs, I'd say you 
hit 
>things right on the money. :)
>
>--DW

--
Jeremy Rand
jrand@xxxxxxxx

Other related posts: