Well, even though the windows build still isn't part of the main trunk, you can still compile it yourself if you use this version: http://code.jellycan.com/memcached/
And if you do that, changing that constant isn't hard. I agree it's not trivial, but it's not hard to overcome if you really need to. /Henrik On Tue, Sep 29, 2009 at 14:35, Josef Finsel <[email protected]> wrote: > Dustin, > > > On Mon, Sep 28, 2009 at 5:44 PM, Dustin <[email protected]> wrote: > >> >> It's a constant that's defined in a header file and is trivial to >> change. It's basically there as a rule of thumb. If you want >> something bigger, you're likely doing something wrong. >> >> > Just an FYI... this is non-trivial for anyone running in a Windows > environment. While I don't disagree that storage of large items is a point > where the developer needs to step back and review their caching, if I *had > * a reason to want larger sizes, I couldn't actually implement them > because I'm constrained by a Windows environment. > > -- > "If you see a whole thing - it seems that it's always beautiful. Planets, > lives... But up close a world's all dirt and rocks. And day to day, life's a > hard job, you get tired, you lose the pattern." > Ursula K. Le Guin > > What's different about data in the cloud? http://www.azuredba.com > > http://www.finsel.com/words,-words,-words.aspx (My blog) - > http://www.finsel.com/photo-gallery.aspx (My Photogallery) - > http://www.reluctantdba.com/dbas-and-programmers/blog.aspx (My > Professional Blog) > > I enjoy the massacre of ads. This sentence will slaughter ads without a > messy bloodbath. >
