All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: obexd: obex_handle_input: poll event HUP ERR
Date: Tue, 22 Jun 2010 17:34:50 +0100	[thread overview]
Message-ID: <1277224491.9334.40.camel@localhost.localdomain> (raw)
In-Reply-To: <4C20E1C8.9020409@gmail.com>

On Tue, 2010-06-22 at 18:16 +0200, Jiri Slaby wrote:
> On 06/22/2010 10:13 AM, Johan Hedberg wrote:
> > On Tue, Jun 22, 2010, Jiri Slaby wrote:
> >> Yeah, -a solved the problem. What does it mean to have an agent
> >> registered? What is agent?
> > 
> > If you don't want obexd to go blindly accepting files from random remote
> > devices you'll probably want some sort of user interaction on the server
> > side, right? One possibility would be to have a GUI process show a
> > "Accept file from ..." dialog every time there's an incoming request.
> > You might also want to choose exactly where on the filesystem obexd
> > stores the incoming file. Such choices would be made by an agent, i.e.
> > a process separate from obexd that has through D-Bus told obexd that it
> > can take care of incoming requests. There's an example command line
> > agent written in python available at test/simple-agent in the obexd
> > source tree. The actual D-Bus API of an agent is documented in
> > doc/agent-api.txt in the same source tree.
> 
> I have gnome-bluetooth-2.30, but I guess it was not converted to act
> also as obexd Agent yet.

gnome-bluetooth doesn't have any Obex server bits. You'd need to use
gnome-user-share to have Obex server capabilities, and it doesn't use
obexd right now, but obex-data-server.

Patches welcome :)

Cheers


  reply	other threads:[~2010-06-22 16:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22  7:23 obexd: obex_handle_input: poll event HUP ERR Jiri Slaby
2010-06-22  7:38 ` Johan Hedberg
2010-06-22  7:41   ` Jiri Slaby
2010-06-22  7:58     ` Johan Hedberg
2010-06-22  8:04       ` Jiri Slaby
2010-06-22  8:13         ` Johan Hedberg
2010-06-22 16:16           ` Jiri Slaby
2010-06-22 16:34             ` Bastien Nocera [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-09-15  7:43 Alex Mach
     [not found] <E1R47Z5-0000QH-00.alexvm12e-mail-ru@f167.mail.ru>
2011-09-16  8:07 ` Luiz Augusto von Dentz
2011-09-21 12:13   ` Alex Mach
2011-09-21 12:33     ` Luiz Augusto von Dentz
2011-09-22  7:40       ` alexvm12e
2011-09-22  8:07         ` Luiz Augusto von Dentz

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=1277224491.9334.40.camel@localhost.localdomain \
    --to=hadess@hadess.net \
    --cc=jirislaby@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.