This I would really like. I wrote a file filter program in three different
versions, a GUI version, a CLI version and Tracker-addon version. The GUI
version had a poorly designed CLI inferface because of the limits of Haiku
reporting if a program was started from the CLI or the GUI.
With this I would only need to write a Tracker-Addon and a GUI program.
Earl Colby Pottinger
On Sunday, March 24, 2019, 9:27:18 p.m. EDT, Ryan Leavengood
<leavengood@xxxxxxxxx> wrote:
Badly coded Tracker add-ons can crash Tracker. Tracker can be blamed
for add-ons crashing, such as in this forum post:
https://discuss.haiku-os.org/t/tracker-crashing-in-hrev52989/8364
I suggest a new server, tracker_addon_host (or maybe
tracker_addon_server) which hosts these add-ons, the same way the
media_addon_server does for media_server.
This server could also expose the add-ons through a command-line
interface, turning all add-ons into command-line tools even if they
were not originally coded for that (I know some are also applications
as well as add-ons.)
The benefits are obviously Tracker can't crash from add-on bugs, and
maybe there is a way for Tracker to inspect the stack trace when the
tracker_addon_host crashes and blacklist the offending add-on.
The drawbacks are of course another server running and more memory
usage, though I doubt it would be too bad. Maybe running the add-ons
over IPC will be slightly slower, but I think the Tracker add-on
protocol is fairly simple, and BMessage passing between apps is well
optimized.
I mention it here to get other opinions on the idea.
This would probably be a fairly fun project. Obviously I am interested
in it, though would not get around to it for a while.
--
Regards,
Ryan
