Two things:
1) When you switch clients, there should be a presence change. On any
presence change, the sender should unlock from the current resource,
and send to the bare JID again.
2) When I switch devices, I'd like to get at least the messages I
haven't seen from the old device to the new device. XEP-146 section
4.2 has a mechanism for this.
I would propose adding text to the XEP to address and clarify both of
these, a more narrative description about locking and unlocking, and
clarifications to how in-order delivery guarantees unambiguous
knowledge of the winner.
On Dec 1, 2008, at 11:45 AM, Dirk Meyer wrote:
Hi,
Jack Erwin wrote:
Message mine'ing provides more of a "do what I mean" experience for
the end user. When he leaves his desk, he will still be alerted via
his mobile client when a new conversation has been initiated, and
will
do it without any sort of preparatory action. If the end user
participates in the conversation, his desktop client will not be
cluttered with the initial fragment of that conversation. As an
added
benefit, if he chooses to ignore the conversation, it will be ready
and waiting on his desktop client when he returns.
I like the idea, but what happens if I switch clients during a
conversation? In your example, we chat with the desktop client. I
think
we are done, but do not close the chat window (I sometimes do that).
Now
I go away with my mobile client. If you send a message now, I guess
the
message will be send to the full JID of my desktop client and I will
not
get the message. Maybe a thread can expire somehow and after a time,
we
should send to the bare JID again doing the whole 'mine' thing again.
Or am I missing something here? I'm do not know the way how chatting
works with full and bare JIDs.
Dirk
--
"[Our enemies] never stop thinking about new ways to harm our
country and
our people, and neither do we." (George W. Bush, August 5th 2004)
