A whiff of citrus – vibrant,
\nshiny, dimpled and thick,
\nyour fingers move, probing
\ntextural ecstacy,
\nas your tastes await
\nthe sweet tartness within.
\nPeel away the layers
\nsoftly, envelop a piece,
\nlet your tongue steep
\nin a myriad of flavors,
\nwith the lingering scent
\nof summer under a blue sky,
\nlook around,
\nand all is well again.
--
\nIf you have any questions or thoughts, don't hesitate to reach out. You can find me as @viksit on Twitter.
","excerpt":"A whiff of citrus – vibrant, shiny, dimpled and thick, your fingers move, probing textural ecstacy, as your tastes await the sweet tartness within. Peel away the layers softly, envelop a piece, let your tongue steep in a myriad of flavors, with the…","frontmatter":{"title":"Ode to an Orange","date":"June 11, 2010","slug":"/blog/ode-to-an-orange","tags":null}},{"id":"06b2ed46-179c-54c4-84aa-5e172c834d62","html":"My last post on the topic was creating a stack implementation using Clojure protocols and records – except, it used atoms internally and wasn’t inherently “functional”.
\nHere’s my take on a new implementation that builds on the existing protocol and internally, always returns a new stack keeping the original one unmodified. Comments welcome!
\n\n(ns viksit-stack\n (:refer-clojure :exclude ))\n\n(defprotocol PStack\n "A stack protocol"\n (push "Push element in")\n (pop "Pop element from stack")\n (top "Get top element from stack"))\n\n; A functional stack record that uses immutable semantics\n; It returns a copy of the datastructure while ensuring the original\n; is not affected.\n(defrecord FStack \n PStack\n (push \n\t"Return the stack with the new element inserted"\n\t(FStack. (conj coll val)))\n (pop \n "Return the stack without the top element"\n\t (FStack. (rest coll)))\n (top \n "Return the top value of the stack"\n (first coll)))\n\n; The funtional stack can be used in conjunction with a ref or atom\n\nviksit-stack> (def s2 (atom (FStack. '())))\n#'viksit-stack/s2\nviksit-stack> s2\n#<atom>\nviksit-stack> (swap! s2 push 10)\n#:viksit-stack.FStack{:coll (10)}\nviksit-stack> (swap! s2 push 20)\n#:viksit-stack.FStack{:coll (20 10)}\nviksit-stack> (swap! s2 pop)\n#:viksit-stack.FStack{:coll (10)}\nviksit-stack> (top @s2)\n10\n</atom>\n --
\nIf you have any questions or thoughts, don't hesitate to reach out. You can find me as @viksit on Twitter.
","excerpt":"My last post on the topic was creating a stack implementation using Clojure protocols and records – except, it used atoms internally and wasn’t inherently “functional”. Here’s my take on a new implementation that builds on the existing protocol and…","frontmatter":{"title":"Stack implementation in Clojure II - A functional approach","date":"June 04, 2010","slug":"/blog/stack-implementation-in-clojure-ii-a-functional-approach","tags":null}},{"id":"10b998e5-0505-5025-bf36-5de7601c5389","html":"I recently started getting a number of SSL related errors on accessing https links with Google Chrome on Ubuntu. One looks like,
\n\n\n107 (net::ERR_SSL_PROTOCOL_ERROR)
\n
The top link on Google’s search results is pretty fuzzy, so here’s the solution that works for me.
\nGo to Settings -> Options -> Under the hood, and enable both SSL 2.0 and SSL 3.0. This should allow Chrome to talk to the server with either protocol.
\nThere’s also a DEFLATE bug that got fixed to solve this issue in release 340 something. http://codereview.chromium.org/1585041
\n--
\nIf you have any questions or thoughts, don't hesitate to reach out. You can find me as @viksit on Twitter.
","excerpt":"I recently started getting a number of SSL related errors on accessing https links with Google Chrome on Ubuntu. One looks like, 107 (net::ERR_SSL_PROTOCOL_ERROR) The top link on Google’s search results is pretty fuzzy, so here’s the solution that…","frontmatter":{"title":"Resolving Chrome's SSL Error","date":"June 03, 2010","slug":"/blog/resolving-chromes-ssl-error","tags":null}},{"id":"34b0c7cf-728d-5c89-8638-3ba9c600c90c","html":"I was trying to experiment with Clojure Protocols and Records recently, and came up with a toy example to clarify my understanding of their usage in the context of developing a simple Stack Abstract Data Type.
\nFor an excellent tutorial on utilizing protocols and records in Clojure btw – check out (http://kotka.de/blog/2010/03/memoize_done_right.html#protocols).
\n\n;; Stack example abstract data type using Clojure protocols and records\n;; viksit at gmail dot com\n;; 2010\n\n(ns viksit.stack\n (:refer-clojure :exclude ))\n\n(defprotocol PStack\n "A stack protocol"\n (push "Push element into the stack")\n (pop "Pop element from stack")\n (top "Get top element from stack"))\n\n(defrecord Stack \n PStack\n (push \n\t(swap! coll conj val))\n (pop \n (let \n\t (swap! coll rest)\n\t ret))\n (top \n (first @coll)))\n\n;; Testing\nstack> (def s (Stack. (atom '())))\n#'stack/s\nstack> (push s 10)\n(10)\nstack> (push s 20)\n(20 10)\nstack> (top s)\n20\nstack> s\n#:stack.Stack{:coll #<atom>}\nstack> (pop s)\n20\n\n</atom>\n More tutorial links on Protocols,
\n\\ http://blog.higher-order.net/2010/05/05/circuitbreaker-clojure-1-2/
\n\\ http://freegeek.in/blog/2010/05/clojure-protocols-datatypes-a-sneak-peek/
\n\\ http://groups.google.com/group/clojure/browse\\_thread/thread/b8620db0b7424712
--
\nIf you have any questions or thoughts, don't hesitate to reach out. You can find me as @viksit on Twitter.
","excerpt":"I was trying to experiment with Clojure Protocols and Records recently, and came up with a toy example to clarify my understanding of their usage in the context of developing a simple Stack Abstract Data Type. For an excellent tutorial on utilizing…","frontmatter":{"title":"Stack implementation in Clojure using Protocols and Records","date":"June 02, 2010","slug":"/blog/stack-implementation-in-clojure-using-protocols-and-records","tags":null}},{"id":"f6ec8ca7-3219-545b-9fea-5e222c4c0e62","html":"Update
\nAs Hans points out in the comment below, it appears pycassa natively supports authentication with org.apache.cassandra.auth.SimpleAuthenticator. Lazyboy on the other hand doesn’t by default.
\nIt’s not too hard to do it though. Intuitively, we could do something like this.
\nNB: Untested code!! I might create a patch for this when I get the time, so this is just an outline.
\n\n# Add this to lazyboy's connection package\nfrom cassandra.ttypes import AuthenticationRequest\n And in lazyboy’s _connect() function, add another parameter called logins, that is a dict of keyspaces and credentials which looks like the following.
\n\n# logins format\n{'Keyspace1' : {'username':'myuser', 'password':'mypass'}}\n \ndef _connect(self, logins):\n"""Connect to Cassandra if not connected."""\n\n client = self._get_server()\n if client.transport.isOpen() and self._recycle:\n if (client.connect_time + self._recycle) > time.time():\n return client\n else:\n client.transport.close()\n \n elif client.transport.isOpen():\n return client\n \n try:\n client.transport.open()\n # Login code \n # Remember that client is an instance of Cassandra.Client(protocol)\n if logins is not None:\n for keyspace, credentials in logins.iteritems():\n request = AuthenticationRequest(credentials=credentials)\n client.login(keyspace, request)\n \n client.connect_time = time.time()\n except thrift.transport.TTransport.TTransportException, ex:\n client.transport.close()\n raise exc.ErrorThriftMessage(\n ex.message, self._servers)\n\n Original Post
\nI’ve been looking to answer which Python library is currently more fully featured to use to communicate with Cassandra.
From Reddit,
\n\n\nAPI-wise, both look like they are pretty much basic wrappers around the Cassandra Thrift bindings. I’d prefer lazyboy over pycassa though, given that firstly, it’s being used in production right now at Digg, and because it looks like lazyboy’s connection code is more featured than pycassa.
\n
and
\n\n\nThe connection code (Lazyboy) seems to be much more suited for use in production (use of auto pooling, auto load balancing, integrated failover/retry, etc.) (than PyCassa)
\n
Thanks to GitHub, I was able to do some analysis of their traffic and commits,
\nIt looks like LazyBoy is probably a better library to start with, for now. I’ll talk about my experiences with both in another post.
\n--
\nIf you have any questions or thoughts, don't hesitate to reach out. You can find me as @viksit on Twitter.
","excerpt":"Update As Hans points out in the comment below, it appears pycassa natively supports authentication with org.apache.cassandra.auth.SimpleAuthenticator. Lazyboy on the other hand doesn’t by default. It’s not too hard to do it though. Intuitively, we…","frontmatter":{"title":"PyCassa vs Lazyboy (updated)","date":"May 21, 2010","slug":"/blog/pycassa-vs-lazyboy-updated","tags":null}}]}},"pageContext":{"limit":5,"skip":100,"numPages":27,"currentPage":21}}, "staticQueryHashes": ["4202924991","512065377"]}