[interfacekit] Re: I'm baaaaaack!

On 2003-08-26 at 06:33:43 [+0200], Erik Jaesler wrote:
> Boy howdy has it been a psycho couple of months for me.  Let's see ...
> got a new job, my family moved, my wife and I are starting a Montessori
> preschool (downside: stressed out wife; upside: got to do a bunch of
> carpentry! =), and I got all ramped up for a masters program.  I've
> finally gotten settled into the job, settled into the new place,
> basically wrapped up prep for the preschool, and I ended up deferring on
> the masters (my wife's still in the middle of hers and there's only so
> much insanity I can take), so I've finally got a bit of time to spare.
> Whew!

Welcome back!

> I did some work on BMessage over the weekend, and I think the public
> interface is now fully implemented, though it's far from fully tested.
> I'm just now writing a test app to do messaging for the first time. =)
> Which brings me to a question.  I start obos_registrar, then I start my
> app, which causes obos_registrar to print "REG:
> B_REG_GET_MIME_MESSENGER" to stdout, then nothing happens.  Both my app
> and obos_registrar just sit there.  I've noticed this is also the case
> with the various BApplication unit tests.  Does anybody know which end
> the problem is on, BApplication or obos_registrar?  Maybe I'll just jury
> rig something with a thread and a semaphore ...

I experienced the same a while ago. IIRC, the cause at that time was, that 
you added the BMessage code to the build, but the BMessage::SendReply() 
methods had only empty implementations, while the private message sending 
methods BMessenger uses were implemented at all, so that the working R5 
methods were used. Hence the application successfully sent the request to 
the registrar waiting for a synchronous reply, which would never come since 
the registrar used SendReply().
So, my suspicion is, that SendReply() doesn't work correctly yet. But I'll 
look into that.

[...]

CU, Ingo

Other related posts: