-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Aug 15, 2012, at 09:45, Yann Leboulanger wrote: > Hi, > > I was wonder what should I do in this situation: > user A and B are connected with resource r1. They that, so messages go from > A/r1 to B/r1. > > user B connects a second client with resource r2 with a higher priority. > > Where should go next message of user A? > > Someone pointed me to XEP-0296 which clearly answer the question: next > message should go to bare JID. > > So I started thinking how to implement this XEP, and came to a problem: > > let's imagine that r2 is LOWER prio than r1. XEP-0296 says that we still need > to go to "unlock state". This mean starting a new thread of course as we > don't know which resource will get it. But if the begining of the > conversation was crypted? or if we negociated the log options or anything in > XEP-0155, then we need to restart the negociation? > Any presence change from another resource for an entity is a change in the user's state. The next message ought to go to the bare JID to allow the infrastructure to account for this change. For encrypted chat, see < http://tools.ietf.org/html/draft-miller-xmpp-e2e-02 > for one approach to the problem. > Same thing if B just go away or na? so we cannot continue en encrypted > conversation if we go away? > Per a separate reply, we can relax this if there is only ever a single resource available. - - m&m Matthew A. Miller <http://goo.gl/LK55L> -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJQK8uOAAoJEJq6Ou0cgrSPnqIH/RyEldOWQhGSt75ckbn02ZrV r46YfQueN9z/C4YFas8PWkr7+pUnXXX7CmWzweaKAuGDNXh3UriWcAL1ov7C1e3D 4YHbv8zTMClq+JxB0sZYvcFJpQgOtWBH4TusX3bSrz+oPWQhGQK+5bUX/Vduc269 aFvE1meJoM8Ia9JNf54e75zWXpFPp7kChwmrJ76FKIfAgSn+08kwhEqI010UXjO5 eUmT0JhXDxy9gWb1xA65PaW/S0xgdiKH1L6iPSv5bAG2yMHLdtG2w1bz+gkE4Qq5 QMFKnMgaS9wUy3EC6i45s2vVIvPmksTwSf9ghtaWvKGLu6M5aiIwClmc/MB/Bm4= =/n8G -----END PGP SIGNATURE-----
