[asterisk-dev] Deprecate non SASL authentication in res_jabber

[Matt O'Gorman]

I dont see having support for the older deprecated mode as too much cruft to have, as well as adding backwards compatibility for older servers.  Maybe at some point in the far future it would make sense to junk it but I think it would be silly to do now

mog
----- Original Message -----
From: "Philippe Sultan" <philippe.sultan at gmail.com>
To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
Sent: Monday, July 2, 2007 8:43:29 AM (GMT-0600) America/Chicago
Subject: Re: [asterisk-dev] Deprecate non SASL authentication in res_jabber

> The important question here: Will it break communication with the
> clients that
> people use? We need to be compatible with existing clients more than
> future
> standards :-)

Yep Olle, being a Jabber client/component, Asterisk always connects as
a client (or a component) to a Jabber server, and therefore does not
deal with authenticating Jabber clients.

So changing the way Asterisk authenticates itself to Jabber servers
won't affect the communication with other Jabber clients, which can
use any other authentication method allowed by the server they connect
to.

Philippe

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev