[Gossip-dev] Re: [Telepathy] GossipProtocol problems

[Mikael Hallendal]

Eitan Isaacson wrote:
> On 10/15/06, Mikael Hallendal <micke at imendio.com> wrote:

>> As for some of the validation, I don't see a huge problem of having it
>> in Gossip. Gossip will know what backends it supports anyway and having
>> implementing some of these (preferably not default server/port) would be
>> okay to do within the Gossip code.
> 
> I agree, although in a perfect implementation we really shouldn't have
> anything protocol-specific in the code.

We will need protocol specific code in the UI layer either way.

>> Same here, it's a requirement. Protocols that don't support it can just
>> return NULL or something and we can simulate only having one resource in
>> the Gossip layer.
> 
> I don't believe this is necessary. What does gossip use this function
> for besides choosing which resource to send the IM to? This is
> determined by Gabble anyway. With Gossip's current functionality there
> is no real need for a Telepathy resources interface. If you decide in
> the future to allow the user to choose the resource he sends IMs to,
> then it would be necessary.

It is used by the UI layer in order to send the message to the right
window. Ie. if we have an active discussion in an open chat window with
someone it is locked to that resource even if another resource with
higher priority comes online.

It should be exported by Telepathy since it is needed by us and will
most definitely be by some other application as well.

Cheers,
  Mikael Hallendal

-- 
Imendio AB, http://www.imendio.com/