[haiku-development] Re: session manager

Ingo Weinhold<ingo_weinhold@xxxxxx> wrote:
> Clemens wrote:
> > In case of tracker thats a bit different. IMHO the problem here is that
> > tracker is a single process but there should be one BApplication for each
> > window. Just another reason for that: tracker add-ons can crash the 
> > complete tracker session, that is bad.
> There are also cons for such a design. Multi-launch would make coordination
> of what directories have been opened significantly more complicated. It
> would also waste resources and make currently Tracker-wide caches (like the
> icon cache and probably also node monitoring) work far less efficiently.
> People more familiar with Tracker might come up with more issues.

Not necessarily more problems (aside from settings being loaded again for each 
new process), but all this could certainly be solved with proper use of shared 
memory. However, there is absolutely no point in doing so: putting Tracker 
windows in separate processes would just be a huge waste of resources (also 
developer resources) without any gain -- opening a window in Tracker would just 
use up more resources and would be slower (due to dynamic binding the 
executable). Future Tracker versions which might use add-ons for their views 
would take an even higher penalty.

Putting the current add-ons in a separate process is a whole different thing, 
though, and certainly a good idea, as they don't need access to any Tracker 
internals and vice versa.

Bye,
   Axel.


Other related posts: