What's probably happening on reload is that you are not terminating the old session, and so ejabberd_http_bind will keep it alive for up to whatever your BOSH wait time is + 30 seconds (default inactivity time).
However, this may not necessarily be a problem. Assuming you're talking about MUC, what version of ejabberd are you running? Since 2.1.9, ejabberd allows multiple sessions from the same user to share a nick. dan On Thu, Nov 8, 2012 at 5:18 PM, Ayukaev Vlad <[email protected]> wrote: > Dear developers, > > I am building a javascript client for ejabberd and want the system to be > fault-tolerant. > However, a user sometimes can accidentally reload the page with the script. > Then when the system reloads it attempts > to join the room again, but gets an error ("This nickname is already in > use"). > Currently, I can imagine using cookie to keep user's jid,rid,sid and > Strophe.connection.attach() to reveal the previous session. > > I also know that recently there were many concerns on this topic, buy I > wasn't able to find any good solutions. > Is there any other ideas how to get away of nickname error? > > Thanks, > > Vlad > > > > > _______________________________________________ > ejabberd mailing list > [email protected] > http://lists.jabber.ru/mailman/listinfo/ejabberd > _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
