Safa wrote: > Hi everyone, > > Sorry for not being able to attend, I had to be afk that time. I have > read the logs and wanted to clarify the xmpp:restart issue about > openfire. > > Because openfire's connection manager is internal, it does not (need > to) actually restart the stream, instead, just sends the stream > features to the client. > > Current implementation which includes my work recognizes xmpp:restart > only when the body does not contain any elements. If the xmpp:restart > body contains any elements (payload), openfire will process it as if > it would process a normal body. > > After some discussion on the list and considering openfire's technical > limitations, this was the best solution we came up with. > > I'll be glad to hear your opinions and try to improve the code > accordingly as I can.
I don't think we'd design it that way now, but it seems to have solved the problem for Openfire. Has anyone seen interop problems with that approach? Peter -- Peter Saint-Andre https://stpeter.im/
