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 tkruthoff@gmail.com designates
 209.85.211.183 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:content-type:content-transfer-encoding
         :mime-version:subject:date:x-mailer;
        b=o5l3bFlLF37htpgTvG183zhy02pkLs07ileo1TS90z3OSQZaCHZ1ljQV1rEwJUKyum
         aFLdeo/h6/WrWmvbmo0YxcEVYCMV1xIWEfaJVKkKF1llaWtyV9WRiUtBnIq4vIzj6vk6
         9JnbnWb07V9+92ItKVWqg7MBanp4nJhtHOYiY=
Message-Id: <E047F0C0-6535-4D74-88A1-41C6992B1867@gmail.com>
From: Troy Kruthoff <tkruthoff@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: atomic/concurrent update_seq for _changes
Date: Sun, 27 Dec 2009 12:36:33 -0800

I have an app that gets data from a view and then monitors _changes  
for updates.  Currently it:

1)  Gets the update_seq from the database
2)  Gets data from a view
3)  Connects to _changes since updae_seq from #1

I'm assuming I need to handle duplicate data, as the database could of  
been modified since the initial get of the update_seq.

What would be sexy is for couch to include an "x-update-seq" header  
for GET requests.  In my case, this would mean 1 less http request,  
and ensure _changes does not include data already reflected in the view.

Thoughts?

Troy