
|
[haiku-appserver]
||
[Date Prev]
[07-2005 Date Index]
[Date Next]
||
[Thread Prev]
[07-2005 Thread Index]
[Thread Next]
[haiku-appserver] Re: App Activation
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-appserver@xxxxxxxxxxxxx
- Date: Tue, 12 Jul 2005 16:02:38 +0200 CEST
Hi Ingo,
Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> 1) The app server needs to receive and process app activations
> requests (as
> issued by BRoster::ActivateApp()).
>
> 2) The app server needs to notify the registrar when the active app
> changed.
>
> The second part should be relatively easy. If the app server is
> started by
> the Bootscript after the registrar (which should be no problem
> anymore), it
> will have a fully working BRoster and can simply send a message to
> the
> registrar (BRoster::Private::SendTo()).
Sounds good, just tell me the message you want to get, and how it
should look alike, and I'll add it to the server :-)
> Regarding the first part, BRoster::ActivateApp() could send the
> request
> directly to the app server. Since there might not exist a
> BApplication when
> the method is invoked, sending it to the port that receives the
> BApplication registration (the one called SERVER_PORT_NAME) might be
> the
> most sensible choice. But I guess you guys know best...
For now that port would be the one to handle these requests, right.
Just add a message code like AS_ACTIVATE_APP to private/headers/app/
ServerProtocol.h and add the calling code to the registrar, and I will
then implement the app_server's part sooner or later :-)
Bye,
Axel.
|

|