[interfacekit] Re: App Server Interface Spec

>>Since I haven't opened my Big Mouth here for a while :-).. :
>Glad you did. :)

Well ok I'll try to whine a bit more often about technical
aspects that seem... wrong-headed even if it's kind of odd
seeing them re-appear every now and then even after they've
been discussed yet... :-}


>>There might be a few things written down here that belong to
>>the registrar rather than the app_server (process management,
>>shutdown ..etc);
>If you could be a little more specific, I'll look into whatever you're 
not 
>sure belongs there.

That's also according to the mail from George H. you once mentionned,
mentionning that start/stopping apps is done by the registrar;
a front-end to the registrar is the BRoster class (just like
BDeskBar is not the deskbar but a "proxy" [is that a design
pattern BTW ? ] to that object).

Talking about the deskbar, it has more info about the
shutdown.. which is performed by the registrar and not
specifically app_server as well:

opentracker/deskbar/BMenu.cpp line 434:
        case CMD_SHUTDOWN_SYSTEM:
                // restart/shutdown
                item->SetTarget(BMessenger(ROSTER_SIG));
                break;

This is easy to find out with a $ grep SHUT *cpp  BTW.

The rest can be left as an "exercise to the reader" :-)
(Ô how rewarding but at the same time horrificly "poser"
is it to say such a thing from a mere mortal 3rd party dev!)


>>But otherwise this sounds good.. the team might want to
>>move to the next step/stage, dunno. (at any rate, know I
>>wouldn't complain if that should be the case).
>Once I understand each area, I think we can progress to tackling the 
use 
>cases. In the mean time, I *am* working on a second, lightweight 
prototype 
>which could be useful down the road for fleshing out.

Ok, your call;

cd.

--
http://cdegea.free.fr/ | BeDev E-16870
"One thing to rule them all" -- UserFriendly.org, 20011021

Other related posts: