richwklein.com » Improving Django Cache – Part II »
Posted By richwklein 3 months, 3 weeks ago in Science & TechnologyIn part I of this series we setup a custom django cache backend based on the current memcached implementation. For the second installment in this series we are going to start modifying our custom cache backend.
Memcached has a couple of limitations it sets on keys. Currently the length limit of a key is set at 250 characters and the key must not include control characters or whitespace. These limitations can be a problem when dealing with long permalinks or rendered template nodes. First thing we need to do is create a method that will fix keys.
Read Full Story at richwklein.com »
100 Views Share Story 0 Comments Report
Submitted By:
richwklein
I am a Senior Software Engineer at Propeller.com. I come from a manufacturing/logistics background, but I've spent the last several years working ...
Who Also Submitted:
More News
Download Squad
Dell snuggles up to Google Chrome OS, offers customized download for its Mini 10V
Watch Ustream over wi-fi or 3G on your Android device
Pie Guy shows off the power of iPhone web apps
MOG announces All Access music subscription service
Seven Mininova and Pirate Bay Alternatives to fend off P2P withdrawal
Engadget
Roomba saves child from deadly Viper, challenges Tango to a fight
Engadget's Black Friday giveaway, part two: win a pack of PSP Go accessories!
Zemno's $500 DeskBook Pro docking station is strictly for zealots
Engadget's Black Friday giveaway, part one: win a Wii Nerf blaster!
FedEx Senseaware tracks everything about your package, probably causes OCD
Submit a Story
Advertisement
Add a Comment
Sign In With Your Propeller Account
Please keep your comments relevant to this story.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.