Aaron,
That's a great suggestion. I'm willing to write the patch accordingly
if I get the green light indicating we can get this into the trunk.
Thanks,
Adrian
On Jul 28, 2009, at 11:04 AM, Aaron Stone wrote:
Maybe more esoteric options should come through a single flag, ala
ssh, where you can have "-o UnusualOption=foo". That reduces the
number of single-letter flags in the command-line flag namespace.
On Sat, Jul 25, 2009 at 2:33 AM, Trond Norbye<[email protected]>
wrote:
On 25. juli. 2009, at 11.14, Toru Maesaka wrote:
G'day!
So I just had a look at the patch and from reading Adrian's reply, I
can understand why such a feature would be handy from hosting
perspective.
The concern is, I think that the majority of users won't need this
feature. That said, it doesn't change the fact that there's a need
for
it so how does this sound as a way to keep things balanced?
Rather than adding it as a user-visible option, would it make
sense to
disable flush_all at build time via configure option? Sure, #ifdef
in
code is ugly but by hiding it from memcached's startup option, this
feature can be provided as an "expert option" who actually know what
they're doing (otherwise it wouldn't be enabled in the first place).
Just an idea :)
Build-time specific options make it harder for people to supply
binary
versions, so I would prefer a runtime option...
Cheers,
Trond
