Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 91191 invoked from network); 18 Nov 2009 22:03:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Nov 2009 22:03:00 -0000 Received: (qmail 57574 invoked by uid 500); 18 Nov 2009 22:02:59 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 57471 invoked by uid 500); 18 Nov 2009 22:02:59 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 57461 invoked by uid 99); 18 Nov 2009 22:02:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Nov 2009 22:02:59 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates 209.85.160.56 as permitted sender) Received: from [209.85.160.56] (HELO mail-pw0-f56.google.com) (209.85.160.56) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Nov 2009 22:02:56 +0000 Received: by pwj6 with SMTP id 6so1022174pwj.35 for ; Wed, 18 Nov 2009 14:02:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=F/1OwcrQBGg7pe+tDfbDvxQpMjdkPLaDo26k7EiRy2I=; b=FysbubiWYLfFyqhVA/tgepwN/GegAB6Vy2kO9rRfDCUbWOaBiISLv5OB/thejvAKdO ErtixxD0mxACSQmThvgXLDdoW+pIyicX9BJ3KXuMWoEnlVyJdK+otZe+/QynmXzZVamW dJmnIjOCrQuphxzHy0JbPMcafWwflHai/bQ8c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=Yy+uxF8dnXeQwp8jf7abt2fPL4nOEZemcmBm4XKr6JmNwjsr5zdexb0zjzslyNA42u y/FyONHPZopdzIrGvl1zVDP/00dznwgECwwoDtTHbyMAvvPY6VhCO7bMIwRlFPnJcOZ6 Viip75CEQ46PMi9C8ESXmk4C9bd7hapg2+NdI= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.142.5.29 with SMTP id 29mr1324562wfe.75.1258581756322; Wed, 18 Nov 2009 14:02:36 -0800 (PST) In-Reply-To: References: Date: Wed, 18 Nov 2009 14:02:36 -0800 X-Google-Sender-Auth: 494cdc4e42b24540 Message-ID: Subject: Re: HTTP session From: Chris Anderson To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Tue, Nov 17, 2009 at 6:39 AM, Vlad GURDIGA wrote: > On Tue, Nov 17, 2009 at 4:28 PM, Jan Lehnardt wrote: >> >> On 17 Nov 2009, at 14:37, Vlad GURDIGA wrote: >> >>> Hello, >>> >>> Do we have the notion of HTTP session for CouchDB? >>> >> >> HTTP is stateless. > > That's true. But then people invented http://www.ietf.org/rfc/rfc2109.txt. :) > > I was referring to that kind of session. Yes, we have various ways to authenticate to couchdb, including a cookie-based auth handler. The underlying tech has been written, but we are still working on a screen for Futon to make it easy to use as a developer. We do try to keep operations stateless, but there's nothing to stop you from using cookie contents in show and list functions, for instance. Just be careful with the cacheing, and patches welcome. Chris > >> >> Cheers >> Jan >> -- >> >> > -- Chris Anderson http://jchrisa.net http://couch.io