On 10/26/07, Alexander Gnauck <[EMAIL PROTECTED]> wrote: > Most implementations send the stream features only once at the > beginning. Because of the missing stream headersin BOSH they send no > stream features after SASL authentication and other stream resets. This > caused me some troubles in the client implementation, because most > clients are waiting for new stream features after SASL authentication. > I think server should send the stream features also in BOSH after all > stream resets (SASL auth) and this should be added o the XEP.
I don't get the problem, the XEP is clear and it requires the client to send a restart in order to get new stream features. If the implementations are broken it's more appropriate to ask the developers to fix them than changing the XEP ;) (there is an historical reason for this problem: most implementations are still compliant to the former xep-124, before the split into xep 124 and 206, where the server was automatically sending the new features; have you tried this one: http://blog.bluendo.com/ff/bosh-connection-manager-update ?) -- Fabio Forno, PhD Istituto Superiore Mario Boella Jabber ID: xmpp:[EMAIL PROTECTED] ** Try Jabber http://www.jabber.org
