Hi, If a client connected to server A is joined into a chat room hosted on server B, and server B takes a dive (hard restart, crash, etc.), who should be responsible for notifying the client of the MUC service interruption? In our case the client is left with a zombie chat room window that will appear alive until they try to send a message to the room and get an error, or some other similar case. Server A knows that server B's s2s connection was interrupted but (in our case) does not track individual users' use of components on server B.
Is there a graceful (and ideally simple) way to inform clients of the interruption immediately? Other than having the MUC service do the equivalent of storing room occupant data on disk, reading it back in during startup after an interruption, and then sending 'unavailable' stanzas out to clients who were previously connected to each room? I'm wondering how server/MUC implementations handle this case, if they do. -Joel
