You seem to-be missing what I'm saying on both points,
On 5-Mar-09, at 12:29 PM, Mickael Remond wrote:
You need both full-jid and sm-id.
My previous post mention that full jid is needed for
"routing" (finding
the session) and sm-id is needed as access key.
The sm-id can include the full jid, you only need the sm-id. But, I
agree it would helpful to server developers to have access to the full
jid when generating the sm-id.
With resource conflict and stream management you most likely don't
want to kick the old session as the original client will want to
resume it. There should a timeout for how long the sm-id is valid
for.
If the session you want to resume as been kicked,
My point is you do not want to kick a session which is being manages,
as the want to resume it at some point.
you probably want to
not allow resuming with old key.
That is stating the obvious.
The xep needs some filling out or maybe be split into two separate
xeps. IMHO, resuming a session is only useful for C2S connections. Why
bother with S2S connections.
ck
