On Oct 5, 2008, at 11:42 PM, Dave Cridland wrote:
On Sun Oct 5 10:33:46 2008, Jonathan Schleifer wrote:
How does replacing the resource work? I thought <conflict/> was
issued
if the resource was in use.
If you get a conflict, you can continue and replace the old resource.
IIRC, with the current RFC, it's undefined what the server does
then, but most replace it. This should be clearified IMO so that
the RFC says it should be replaced then.
FWIW, we conflict. I have some ideas for how to do replacement
sensibly, but terminating a live client means risking the ping-pong
effect that server administrators hate.
Sure, but such client is broken if he does not respect the stream
error condition <conflict />.
A proper client, if he receives a <conflict /> stream error MUST NOT
reconnect.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: [EMAIL PROTECTED]
Use XMPP!
