Re: obexd: obex_handle_input: poll event HUP ERR

[Johan Hedberg <johan.hedberg@gmail.com>]

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.

Johan