On Aug 7, 8:49 pm, Michael Shadle <[email protected]> wrote: > >> 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
I wrote a java api for it a while back, but pulled it out of my client because I didn't think it was responsible to ship my client with support for it -- people kept trying to use it and thinking it was supported. > 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) I agree. If someone can't perform a task correctly, train the person or give the task to someone who can.
