Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of kallin.nagelberg@gmail.com
 designates 209.85.210.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=I1nVlcqDj87xE2EUeRMo+KJyHgTgb6gcCsHPUn1+X0gCdBgyAFEIH/2Niw5jIhR4Nt
         Gilwe7ucuI113J8Ao5itYRCcQDjz3kOQYzYB+ES3rC730DYvfANAvjrLQQbT8MlodZ3N
         6qPZWSUO2DmeQM8+Cv6mDT91+5IjP4w28MJdY=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=O6tsxLUZNbTDSF-epyW4vJx1TMunNhmN+WAFq@mail.gmail.com>
References: <AANLkTinfBRBCCYLfUDJhg1sWmcxefJOFAT8UVqPQXPhC@mail.gmail.com>
 <1296582141589-5981961.post@n2.nabble.com>
 <AANLkTi=F7hF0eUZv8SrnpBUULYVE3fZYJqLxNPGAD_F9@mail.gmail.com>
 <1296583033554-5982024.post@n2.nabble.com>
 <F1ADABBBB05C564281981ED6717917D004205FAAE3@MAILCA6.rms.com>
 <AANLkTimz-340Vt-xsc1NsoAOr5+H63124SBL=u1z88YT@mail.gmail.com>
 <AANLkTi=O6tsxLUZNbTDSF-epyW4vJx1TMunNhmN+WAFq@mail.gmail.com>
From: Kallin Nagelberg <kallin.nagelberg@gmail.com>
Date: Tue, 1 Feb 2011 15:10:50 -0500
Message-ID: <AANLkTin_f4iAGeVLkT4NbW4XKRhquvuavpsKfms6QWEG@mail.gmail.com>
Subject: Re: cassandra as session store
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Reddis seems neat, but a couple issues:

- It's 'persistence' is more of a timed backup. You are not guaranteed
the latest results on disk.
- no real 'clustering'. It has a master/slave system.

Hard to say if those are deal breakers at this point, but the API for
it seems nice.

On Tue, Feb 1, 2011 at 1:48 PM, Kallin Nagelberg
<kallin.nagelberg@gmail.com> wrote:
> Hmm, looking at redis now. The built in time to live functionality
> would be nice to have..
>
> On Tue, Feb 1, 2011 at 1:34 PM, Colin Vipurs <zodiaczx6@gmail.com> wrote:
>> Wouldn't something like Redis be a better fit than Cassandra?
>>
>> On Tue, Feb 1, 2011 at 6:16 PM, Tong Zhu <Tong.Zhu@rms.com> wrote:
>>> If it is a really session data, which will be active for a short time, =
a few hours, and it is OK to lose them, memcached is a better solution. I w=
ere using it when I was in Yahoo.
>>>
>>> Tong
>>>
>>> -----Original Message-----
>>> From: buddhasystem [mailto:potekhin@bnl.gov]
>>> Sent: Tuesday, February 01, 2011 9:57 AM
>>> To: cassandra-user@incubator.apache.org
>>> Subject: Re: cassandra as session store
>>>
>>>
>>> For completeness:
>>>
>>> http://stackoverflow.com/questions/3746685/running-django-site-in-multi=
server-environment-how-to-handle-sessions
>>> http://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cached=
-sessions
>>>
>>> I guess your approach does make sense, one only wishes that the servlet=
 in
>>> question did more work for you. If I read correctly, Django can cache
>>> sessions transparently in memcached. So memcached mecomes your Session
>>> Management System. Is it better or worse than Cassandra? My feeling is =
that
>>> it's probably faster and easier to set up.
>>>
>>>
>>> --
>>> View this message in context: http://cassandra-user-incubator-apache-or=
g.3065146.n2.nabble.com/cassandra-as-session-store-tp5981871p5982024.html
>>> Sent from the cassandra-user@incubator.apache.org mailing list archive =
at Nabble.com.
>>>
>>>
>>> This message and any attachments contain information that may be RMS In=
c. confidential and/or privileged. =A0If you are not the intended recipient=
 (or authorized to receive for the intended recipient), and have received t=
his message in error, any use, disclosure or distribution is strictly prohi=
bited. =A0 If you have received this message in error, please notify the se=
nder immediately by replying to the e-mail and permanently deleting the mes=
sage from your computer and/or storage system.
>>>
>>
>>
>>
>> --
>> Maybe she awoke to see the roommate's boyfriend swinging from the
>> chandelier wearing a boar's head.
>>
>> Something which you, I, and everyone else would call "Tuesday", of cours=
e.
>>
>