On Apr 17, 2008, at 02:30, Veit Zimmermann wrote:
> May I summarize. I have three options:
>
> 1. Continue to use "high level commands" (Open) and abort and tell the
> user, if the server does not support authentication.
>
> 2. Offer an option to use no authentication.
>
> 3. Chang to more basic functions and switch to no authentication in
> case
> of none available.
>
> Oh, by the way: I use V5 in this project.
> Thanks to all of you!
I would suggest #2: Let the user select in your application whether
they want authentication or not. However, if they want authentication,
and the server does not support it, you should let it fail and then let
the user take action. If a user is expecting a secure environment but
the server does not support it, I do not think the application should
just silently ignore this.
This is the behaviour of common mail clients right now. In
Thunderbird, for example, if I set it to use authentication and the
server does not support it, it will fail sending e-mail, and that's it.
I have to actively go and change my configurations to either use a
different server, or disable authentication.
I think Arno also agreed that this is the proper behaviour.
dZ.
--
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
