Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of jens@couchbase.com designates
 206.225.164.31 as permitted sender)
From: Jens Alfke <jens@couchbase.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Date: Wed, 13 Feb 2013 21:18:06 -0800
Subject: Re: replication on touchdb and authentication
Thread-Topic: replication on touchdb and authentication
Thread-Index: Ac4KcquuCz7NMf61SsarOP/1dC2pAA==
Message-ID: <D1ACE206-860F-4BDB-93AC-F42B7BDAFD70@couchbase.com>
References: <mskohdpthvh4067d5lvamgnj.1360809226494@email.android.com>
In-Reply-To: <mskohdpthvh4067d5lvamgnj.1360809226494@email.android.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On Feb 13, 2013, at 6:33 PM, Svilen <az@svilendobrev.com> wrote:

> Unless the cookie life is 1 year. Its config anyway.

OK, if you control the server you could do that. (Though of course the clie=
nt app=92s HTTP framework could drop the cookie at any time; that=92s withi=
n spec.)=20

But I=92m not sure what your point is. You can=92t code a client app withou=
t considering credentials. The cookie has to come from somewhere, so the ap=
p has to be able to log in. What is it going to save you to store a cookie?

Anyway, no, TouchDB does not support logging in using _session, except as a=
 side effect of using BrowserID. If you think it really needs to, the code =
is open source so you=92re welcome to add that feature.

=97Jens=