Re: [Bluez-devel] CUPS plugin discovery bits

Bastien Nocera
2007-05-23T16:15:24Z

On Wed, 2007-05-23 at 17:51 +0200, Marcel Holtmann wrote:
> Hi Bastien,
>
> > Here's a patch against CVS bluez-utils to add discovery to the CUPS
> > backend. With this, it means that most CUPS front-end will be able to
> > list visible printers when adding a new one, be it through the web
> > interface or other front-ends (like Fedora' system-config-printer).
> >
> > It adds D-Bus and glib as dependencies for the backend (not that it
> > matters that much...).
>
> it actually does. We provide an eGlib for embedded systems and so when
> compiled with GLib, we only use that function subset.
>
> And second you use the GLib D-Bus bindings. I am not willing to create
> these dependencies for a "daemon" package.

It's not a "daemon", as in, it won't be running all the time. It's only
a small short-lived program. Should I make it compile-time dependency?

> Another small thing is that DisocverDevices() will automatically take
> care of the name resolving for you. So no need to call GetRemoteName().
> You will get the RemoteNameUpdated() signal.

Cool, I'll clean up the code.

> The thing that worries me is when you start CUPS it will list through
> all backends and make them list. So on every boot the system will scan
> for devices in range and that can slow down the system boot. So this
> might not be a good idea. Actually that is the reason why we wanna go
> for a printing service in the future.

As Tim mentioned, CUPS won't do the requests on startup, but on demand.

As for the printing service, what would it actually buy us, ie. which
feature would you have in it that aren't possible in the backend?