Comment 9 for bug 197323

I think that I need a new kind of abstraction for the connection
options in this case. I wasn't too happy with the existing one which
reads:

# -digest 0|1 (means if password
should be hashed in old jabber way)
# -secure 0|1 @@@ Change this to -xmpp ?
# -method ssl|tlssasl|sasl

#
# o Note the naming convention for -method!
# ssl using direct tls socket connection
# it corresponds to the original jabber method
# tlssasl in stream tls negotiation + sasl, xmpp compliant
# XMPP requires sasl after starttls!
# sasl only sasl authentication
#
# o @@@ Perhaps a better way is to use a -xmpp switch that sets
# the main mode of operation, and then use whatever as
sub switches.

As I indicated above, perhaps it would be better using another
abstraction where I first decide if connecting using old jabber way
(-xmpp 0) or the xmpp way (-xmpp 1), and then have switches that pick
the details of each mode like SASL, TLS etc. But the user should never
bother picking the mode, just the degree of security wanted. Need to
think...