Christoph Schmidt wrote:
As far as I see, the presence of a 'version=1.0' attribute in the
opening stream tag doesn't indicate that you MUST NOT use
jabber:iq:auth. It does indicate that there might be more suitable
options available, because the presence of 'version=1.0' indicates
that TLS/SA
Hi, thanks for the quick responses.
I'm replying here though Guus has a very good argumentation about the
reasoning behind this behavior.
Am Dienstag, den 13.09.2005, 15:01 +0200 schrieb Alexander Gnauck:
> Stefan Strigler schrieb:
> > Or let me rephrase to make it more clearly: A client may us
As far as I see, the presence of a 'version=1.0' attribute in the
opening stream tag doesn't indicate that you MUST NOT use
jabber:iq:auth. It does indicate that there might be more suitable
options available, because the presence of 'version=1.0' indicates that
TLS/SASL is implemented, as desc
Hi Stefan,
First off, you need to be warned that I'm not blessed with any
experience in jabber just yet. I'm busy educating myself by reading into
the xmpp and jabber protocols. Please take my comments with that in
mind. If other readers spot errors in my explanation, please don't
hesitate to
Hi Steve,
Stefan Strigler schrieb:
Hello list, is it correct behavior that if asking a server for stream
features by supplying a "version='1.0'" to the opening stream tag like
and the server indeed is capable of doing SASL authentication it may not
accept a jabber:iq:auth style type of authen
