Date: Wed, 21 Feb 2007 08:44:51 -0800 From: "Maksim Yevmenkin" <maksim.yevmenkin@gmail.com> To: "Iain Hibbert" <plunky@rya-online.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp 1.4.5 Message-ID: <bb4a86c70702210844s5de96547ub826c4f95258d7e2@mail.gmail.com> In-Reply-To: <1171994649.866710.8121.nullmailer@galant.ukfsn.org> References: <bb4a86c70701300920g47111252n9c50cef20221973a@mail.gmail.com> <bb4a86c70701301952y322a5174m762889c986986768@mail.gmail.com> <1171994649.866710.8121.nullmailer@galant.ukfsn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Iain, > It would be good if the manpage could mention that for server mode, it > might be necessary to also set the "Object Transfer" bit (0x100000) in the > class of device. eg, my Nokia 6103 filters out devices that do not have > that bit set during discovery.. ok, i will add this to the man page. > I do not really understand the -f option, client mode does not seem to > work without it when sending files to my phone.. -f means connect to "file browsing service". basically it will make obexapp to put additional header into connect request. obexapp can be used to do both obex push and obex file transfer. if both services are running on the same rfcomm port then extra header in the connect request can be used to identify which service client is requesting. it somewhat similar to the host: header in http. so, if you are connecting to obex file transfer service, -f option is required (assuming that obex server was properly implemented) thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70702210844s5de96547ub826c4f95258d7e2>