Forcing tp-fs to track the self handle, group or otherwise in the senders group is too complex. I don't to have to track handles and stuff in tp-fs. And I don't want to differentiate between Group and non-Group channels. There should be a simple "Sending" property on the Stream.I.Media interface We should also add a "Receiving" property, this would help with bug #28707.
(In reply to comment #0) > Forcing tp-fs to track the self handle, group or otherwise in the senders group > is too complex. I don't to have to track handles and stuff in tp-fs. And I > don't want to differentiate between Group and non-Group channels. > > There should be a simple "Sending" property on the Stream.I.Media interface Wouldn't something like a (Start)Sending signal be better? If you have the property then you'll already have to have change notification for you to know when to start sending, so we could just leave it with the signal? > We should also add a "Receiving" property, this would help with bug #28707. Same here.
I want a property with change notification, there is a PropertiesChanged signal on the standard dbus Properties interface now. The reason to have a property, not only a signal, is that otherwise the CM has to know when you start listening. Also, you want a 3rd party to be able to look in and see what the current status is.
This is what I'm adding: http://people.freedesktop.org/~jonny/telepathy-spec-call/spec/Call_Stream.html#org.freedesktop.Telepathy.Call.Stream.DRAFT.LocalSendingState pending review from Sjoerd.
SetSending() should probably be in the Media Interface, not the UI-facing one.
Fixed in git.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.