Recently in developer Category

At OthersOnline we make heavy use of memcached, memcachedb and memcacheq. While in general all of these work and work well, we're learning that many of the memcache client libraries (we're using spy) may have been developed with the assumption that the backend you are interacting with operates as a cache.

Individual messages may or may not be treated as the precious, valuable nuggets of data that no doubt they are. Individual backends may be assumed down for lengthy periods of time regardless of actual state. While in general I like memcacheq and would love to try out kestrel, the fact that both rely on a memcache client library gives me pause.
If you are going to write a queue service, for frack's sake please include a getQueueSize() method in the API. Make it fast and make it an estimate if you have to, just get 'er done.

Recent Activity

  • Sam tweeted, "finally took the time to disable google's annoying search results click tracking:"
  • Sam tweeted, "if you have never tried it, I do not recommend sharing a laptop with your spouse. supply/demand curve all out of whack."
  • Sam tweeted, "the first world is the new third world: woman in San Miguel County cannot even collect her own rain water."
  • Sam tweeted, "reading about neuroenhancers in the new yorker. classic arms race: we're all better off if nobody takes these."
  • Sam tweeted, "Heading to Remlinger Farms for our annual mother's day visit."
  • Sam tweeted, " - Dust mite poop from our mattress"
  • Sam tweeted, "In the absence of other information, one way to judge a restaurant is by it's distance from a gas station. More is better, fyi."
  • Sam tweeted, " - IMG00127.jpg"