From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Error.InProgress forever after DBus timeout on GetRemoteServiceHandles
Date: Tue, 15 May 2007 17:33:42 +0200 [thread overview]
Message-ID: <1179243222.10069.26.camel@violet> (raw)
In-Reply-To: <4649CC21.2070701@idlum.be>
Hi Pierre-Yves,
> I perform a call on GetRemoteServiceHandles. For some reason it fails
> with a DBus timeout. After it has happened, each subsequent call to
> GetRemoteServiceHandles about this device result in a Error.InProgress.
>
> More precisely, my code tried it 36 times over about 7 minutes, and it
> failed that way each time.
>
> What should I do in such a case? It should somehow effectively timeout,
> or there should be a way to cancel it. I didn't find any in the
> dbus-api.txt file.
from the hcid side it is impossible to know when the request fails due
to a timeout. However calling the FinishRemoteServiceTransaction method
should cleanup the state and make it usable again. If not, then that is
a bug.
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
prev parent reply other threads:[~2007-05-15 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 15:05 [Bluez-devel] Error.InProgress forever after DBus timeout on GetRemoteServiceHandles Pierre-Yves Paulus
2007-05-15 15:33 ` Marcel Holtmann [this message]
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=1179243222.10069.26.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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