[haiku-commits] Re: haiku: hrev49583 - in src: servers/launch kits/app
- From: Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Fri, 28 Aug 2015 10:39:30 +0200
Am 28/08/2015 um 10:14 schrieb Ingo Weinhold:
On 28.08.2015 09:35, Axel Dörfler wrote:
It's not something I'd like to lose. I would rather invent some
mechanism to overcome the team ID issue, like placeholder teams, that
will automatically resolve to the assigned team. Once a team starts it
would need to take over all of its areas, ie. a mechanism similar to
fork(), just with completely different semantics.
Wouldn't it suffice to call load_image() but wait with actually resuming
the main thread? Not exactly placeholder teams, but already pretty close.
As a temporary workaround, this might work, too. For long term, I think
this would bind too many resources for jobs that might never run.
For example, the print server will only be started on demand in the
future, but might never be used.
But on second thought, and for the time being, since the port is
retrieved via the launch_daemon anyway, and the GetLaunchData() reply
will wait for the team to be launched now, it could now also just return
the actual port within the team.
Long term, this is not the optimal solution, though, as it would be nice
to send a message to a team without having to wait for it to be started,
ie. send the message and go on. Not all messages need an immediate
reply. Also, another idea was to keep the team available even if it
crashed; ie. the team could be relaunched, and no messages would have
been lost in the mean time -- at least for some things this would make a
difference without further effort (like Tracker, the authentication
manager, ...).
Bye,
Axel.
Other related posts:
