On Sat, Aug 7, 2010 at 8:31 PM, Dustin <[email protected]> wrote: > Note that SASL does allow username/password and many other types of > authentication. If your app uses long-lived connections (as they all > should), authentication doesn't make it more slower in any meaningful > way.
If using persistent connections yes, only initial negotiation would be impactful you're right. >> I won't be able to use remote debug or dump the cache. > > You can't do it now. Brian said you can dump the cache... My notes from OSCON: "you can dump your data using "memdump" - pulls back a meg worth of keys, also has a C API for it" so it sounds like you -can- not that you have a legitimate reason to need to... :p (yes it's sort of not really the point.) Also the whole "you should display warnings" thing is -annoying- I have an open with mod_passenger folks because starting nginx with mod_passenger compiled in, but not actually activated results in a warning about "hey, you have passenger compiled but not enabled" I can't even think of a proper metaphor for that. Obviously if you your app isn't working, -maybe- you didn't configure it properly in the webserver... at some point you have to stop treating administrators and such as idiots. If they -are- idiots hopefully they get demoted or fired. Not hope that the software is so overly verbose about everything it prods you along with everything (and where do you stop? Someone else will want more than a notice about binding IP addresses. They'll want something telling them "hey you could use more RAM for the cache" or who knows what else) There's a reason you interview someone and look for their skills for a position. Otherwise we could go hire a hobo on the street for as little as possible just to have a warm body pushing buttons.
