http://bugs.freedesktop.org/show_bug.cgi?id=18323
Summary: Connection Manager parameter docs should be online
Product: Telepathy
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
On Wed, 2008-10-29 at 11:20 +, Will Thompson wrote:
However, I tried this, and I just get
StatusChanged(Connecting, Requested),
StatusChanged(Disconnecting, Requested)
That's because your example was calling Connect(), then immediately
calling Disconnect(). So, it had indeed
On Wed, 2008-10-29 at 15:04 +1100, Jiri Baum wrote:
There'd also be nothing to stop a CM having the wrong type for a
well-known parameter - we'd consider it to be buggy, but that's no
reason to let it crash client code remotely.
I think you should check for that when initializing the
Hello,
Telepathy-SofiaSIP development release 0.5.11 is available:
https://sourceforge.net/project/showfiles.php?group_id=191149package_id=256956
New in this release:
* Migrated the source repository to Git.
* Updated to telepathy spec 0.17.13.
* Improved handle normalization.
*
http://bugs.freedesktop.org/show_bug.cgi?id=17330
Mikhail Zabaluev [EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Hello,
I think you should check for that when initializing the connection
manager. Constraints are good.
Jiri:
You can't really do that when initialising the connection manager,
because the application doesn't do that - the MC does. The MC might
consider a different set of parameters
On Sat, 2008-11-01 at 00:02 +1100, Jiri Baum wrote:
The telepathy spec (and the telapathy-glib documentation) documents
the
well-known parameters. So those are the ones that should be checked.
I expect this set changes slightly between versions?
All the more reason to check that the CM
