Hi Alex, On 10/26/07, Alexander Gnauck < [EMAIL PROTECTED]> wrote: > > Hello, > > i recently finished my BOSH implementation and stumbled over 2 problems. > > 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 think the problem is necessarily the XEP. Although it does not seem to mention the need to send stream:features, they are shown in an example. The Real Problem is that many implementations simply do not understand the stream restart request. Could this be the problem you are seeing? The status a while ago among servers as I found it is documented here: http://matthewstechnologyblog.blogspot.com/2007/07/summer-of-code-progress.html and here: http://matthewstechnologyblog.blogspot.com/2007/08/summer-of-code-update.html Possibly some servers have changed since I tested them. For me Fabio's CM was working the most reliably, and Openfire without pipelining or SASL. I have not tested the new Tigase server BOSH implementation... it's on my todo list. I think after termination of the BOSH session the server should close > all open webrequests. The most servers wait until they time out now. Seems common sense, yes. Matthew.
