If I explicitly override the default, by explicitly requesting
'clear', because my requirements explicitly need this ability, then
I must change the code to get rid of the warning? Ahh, but it's for
the 'simple', who must be guided, and can't be bothered to read the
warnings in the text so bonk'em repeatedly in the logs till they
mind what you say. Which is to explicitly not use the feature which
you've explicitly provided? (sigh)
How about adding 'clear_please_please' ?
(Just because I like simple doesn't mean I _am_ 'simple' - and I
really do appreciate the simplicity enablers, really)
Hi Thomas,
I understand. The SimpleDB will only complain upon starting the app.
If you really can't have the warning, you can use the 'standard'
password credential and the 'normal' auth config method, you will get
no warning on 'clear' as the password type.
Matt suggested a way to turn off the warning also... but I am
skeptical... either we hold the newbies hand and protect him from
himself, and warn him if he's doing something dangerous.... or we
happily let them shoot themselves in the foot, assuming they'll
probably figure it out after the first time.... Seems the two options
are out of sync with each other...
I'm not beyond convincing... just a bit skeptical.... Anybody else
want to weigh in... should we protect them, but allow them to throw
off the comfort blankets if they say 'PLEEEEEeease'?
Jay
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
