From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: twaugh@redhat.com
Subject: Re: [Bluez-devel] CUPS plugin discovery bits
Date: Wed, 23 May 2007 17:51:11 +0200 [thread overview]
Message-ID: <1179935471.19944.6.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <1179933855.3629.75.camel@cookie.hadess.net>
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.
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.
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.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-05-23 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 15:24 [Bluez-devel] CUPS plugin discovery bits Bastien Nocera
2007-05-23 15:51 ` Marcel Holtmann [this message]
2007-05-23 15:57 ` Tim Waugh
2007-05-23 16:15 ` Bastien Nocera
2007-05-23 16:26 ` Bastien Nocera
2007-05-23 16:56 ` Johan Hedberg
2007-05-23 17:07 ` Bastien Nocera
2007-05-24 13:39 ` Bastien Nocera
2007-05-24 15:31 ` Johan Hedberg
2007-05-24 18:49 ` Bastien Nocera
2007-05-25 12:30 ` Bastien Nocera
2007-05-25 12:58 ` Bastien Nocera
2007-05-25 15:08 ` Bastien Nocera
2007-05-29 3:58 ` Luiz Augusto von Dentz
2007-05-29 10:26 ` Bastien Nocera
2007-05-29 13:18 ` Luiz Augusto von Dentz
2007-05-29 13:37 ` Marcel Holtmann
2007-06-07 10:21 ` Marcel Holtmann
2007-06-07 12:59 ` Bastien Nocera
2007-05-24 15:03 ` Bastien Nocera
2007-05-24 15:20 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1179935471.19944.6.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=twaugh@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox