On 2013-01-26, at 1:30 PM, Dave Cridland <[email protected]> wrote: > And interesting issue, though, is that the generic failure case with > 198-ack-only is that stanzas are duplicated, whereas without any 198, the > generic failure is loss.
In theory, but it all depends on how any implementation defines handled. If the spec defines how to handle specific cases then you are there. Also, it would be helpful define what would be the desired behaviour in a number of different failure cases. For example, when a message being sent to a remote MUC room fails, the client should silently try to rejoin the room then resend the message. If two servers which support resumption and the connection drops between them. They should not remove those remote users from MUC rooms until the resumption session times out. With enough examples it should be clear to implementors how their products should behave. ck
