Re: Jabberd2 client issues (jabber-2.0s1)
Robert Norris <rob <at> cataclysm.cx>
2004-01-02 00:23:47 GMT
On Thu, Jan 01, 2004 at 01:34:50AM +0100, Matthias Wimmer wrote:
> Robert Norris schrieb am 2004-01-01 10:52:12:
> > Can someone give more information on what a "quick login" is, exactly?
> > I've never heard of it before.
> As this was in the mailing list just a few days ago, I asked this as
> well. I think I got the answer or a pointer to something that told me,
> that it does not work if the client sends the authentication stanza in
> the same TCP packet as the stream start. But I do not know why this
> should be a problem. I have not checked if this is really a/the problem.
Assuming this is a "quick login", I would note the following:
- This isn't really any quicker, as the client still has to receive the
stream response, auth result, etc before it can do anything useful.
- Its pretty bad form on the part of the client to assume that the
stream will always be successfully established. And with XMPP making
error conditions so much more explicit, you really can't afford to
not be watching for errors every step of the way. I consider your
client to be broken if its not doing this.
- jabberd2 takes steps to handle packets that arrived before the stream
was established - they get queued until the stream is fully open (ie
the stream response has been returned to the client), then replayed.
This is a hack, but is needed for quite a few broken clients.
However, it hasn't been well tested, so there may be a bug there.