[jdev] s2s connections and presence

[Norman Rasmussen]

On 5/19/06, Wendell Turner <wendell at adsi-m4.com> wrote:
> Question 1:
> Is this how it is supposed to work?  Is this behavior affected
> by the queuetimeout or idletimeout in the s2s section of the
> config file?
This is how it works at the moment.  (not sure how much it's by design
choice, or how-it-happens to work)

> Would other servers (jabberd2, ejabberd) behave differently
> (i.e., remove the presence indication when s2s tcp connections
> die)?
I think they do, yes.

> Even when romeo tries to send a chat msg, an error is evenutally
> sent back to the client, yet still the presence doesn't change.
unfortunately that's the way it is at the moment.

> Question 2:
> Both montague.com and capulet.com try to establish tcp
> connections to each other, but are unsuccessful (Verona's
> network is down).  When Verona's networks come back up, what
> mechanism in either server causes presence to 'reconnect'?
there is none.  (this is probably an implementation consideration,
most implementations drop the packets, and give up)

> If either romeo or juliet sets their status to offline, then
> back to online, that triggers the servers to re-try the
> connections, but will the servers do it by themselves?
implementation specific, most don't at the moment.

There's an assumption in the xmpp spec that all servers are 'well connected'.

If a servers IP changes often (like eg: it's on a 24hr dhcp licence
via adsl), then there are issues - depending on which servers, how dns
is set up, etc.

If links are 'dead' between servers, then the data just doesn't make
it, and the server state hasn't changed.

-- 
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/