## DBUS Backends

Backend helpers communicating over standard out and standard error are easy to write, but can have some performance problems. For instance, if your packages system has to do a lot of work when it starts up and shuts down, performance in the UI may suffer. In these cases, you can use a persistant backend daemon that communicates to the C backend over DBUS.

Your daemon will be started by DBUS, and should be responsible for it's own thread management. It should receive an `Init()` method call when the C backend starts, and an `Exit()` method call before it exits. You should also consider adding a timeout value to your daemon so that it will exit after a set time with no activity from the C backend. That way the daemon will still exit even if the C backend crashes for some reason.

Again, like the helper backends described above, a compiled backend stub is needed. An example of a DBUS backend written in python can be found in `backends/apt`, along with a compiled stub written in C.