[Telepathy] RFC: draft chat state interface specification
Luiz Augusto von Dentz
luiz.dentz at gmail.com
Thu Oct 19 12:22:41 PDT 2006
On 10/19/06, Robert McQueen <robert.mcqueen at collabora.co.uk> wrote:
> We found a thread about chat states in the archives which kinda died
> out, so I thought I'd resuscitate it. The patch from Luiz  looks
> reasonable - I agree that the original proposal  didn't make it clear
> that the state was per member rather than for the entire channel. Maybe
> "Member State" would be better interface name? Also, if the interface is
> not going to be entirely chat-specific, the descriptions should be
> modified to not refer to "chat", but "channel".
I agreed with MemberState if we are planning not only use it to chat states,
but Im not sure if other channels can and will use it. Another thing is
interface may confuse the applications, it has to be clear that this is to
with notifications not presence and others possible states, because that it
be a good idea to add Notification so it becomes MemberStateNotification.
Also there is in Channel.Type.Text interface a type called
CHANNEL_TEXT_MESSAGE_TYPE_NOTICE that we could use if we found
just chat has this type of notifications.
I would like to raise another question here, why telepathy dont use
mechanism like publish/subscribe/notify that SIP has. I find it much simpler
and also pretty extensible.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Telepathy