[Telepathy] StreamedMedia/Call spec ambiguities

[mikhail.zabaluev at nokia.com]

Hi,

> -----Original Message-----
> From: telepathy-
> bounces+mikhail.zabaluev=nokia.com at lists.freedesktop.org
> [mailto:telepathy-
> bounces+mikhail.zabaluev=nokia.com at lists.freedesktop.org] On Behalf Of
> ext Olli Salli
> Sent: Monday, April 04, 2011 4:24 PM
> To: David Laban
> Cc: telepathy at lists.freedesktop.org
> Subject: Re: [Telepathy] StreamedMedia/Call spec ambiguities
> 
> Following IRC discussion, let me condense the current issues with
> StreamedMedia and its Gabble implementation into a few bullet points:
> 
> - Is the direction of a stream in a StreamedMedia channel a valid
> concept unless the Stream is in state Connected?

Specifying that a CM should emit StreamDirectionChanged with actual direction (if different from the assumed Receive/PendingLocalSend) before signaling the stream as Connected could be a useful cop-out for clients who are not requesting the streams and only receive the signals.

> - What should the direction be reported as for a freshly requested
> stream for which we don't yet know if the remote user accepts to send
> on, or even can send?

Telepathy-Rakia should return the stream with direction Receive and the Pending_Remote_Send flag.
What Gabble does is probably bong, ignored by all clients because they really listen for StreamHandler signals.

Best regards,
  Mikhail