On Thu, Oct 21, 2010 at 4:28 PM, Will Thompson <[email protected]> wrote: > On 21/10/10 15:47, Tomasz Sterna wrote: >> >> On czw, 2010-09-16 at 09:38 +0100, Will Thompson wrote: >> >>> >>> 1. Assign the new client a fresh resource; >>> 2. Boot the old connection, granting the resource to the new client; >>> 3. Refuse the new connection. >>> >>> I don't really think behaviour 3 is very useful. >>> >> >> a. Protects you from rerunning the same client with the same >> configuration more than once. >> >> b. Protects you from #2 disconnect-dance if both clients are configured >> to reconnect on disconnection. >> > > I'd argue that any reasonable client should do the right thing (that is: not > reconnect until explicitly told to) if it's booted for reason <conflict/>. > :)
Or, the more sensible response... How does the server tell the client that the resource is now available if the client doesn't try to reconnect? /K _______________________________________________ JDev mailing list Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
