creating single (or 2) -tear applications is in my view the main point of couchdb. last year i did a prototype combining gwt and couchdb. (just a hack to proove the combination of gwt, json an couchdb)
source is available at http://github.com/tbaum/gwt-couchdb it's a maven-project so type 'mvn install' and './push.sh' to get started.. i used gwt-mosaic, don't worry about the gwt-compiler warnings (and i don't really recommend using moasic anymore!) to help development and get rid of the same-origin-policy, i created a small proxy-servlet. so you can debug your app in your ide when compiled an uploaded it will run just in couchdb and your browser http://127.0.0.1:5984/gwt/_design/couch/index.html hope that helps, thomas == i didn't follow the mailinglist and don't know the current state: at the time(08/2009) developingthe prototype i came to the point, that we could not use couchdb in 'real world' - deployment issues (plattform dependencies, erlang wont run 100% on the m$ boxes..) - missing security model (also for restricting read access) - from time to time i got errors from the view-cache (.. sorry no time to reproduce)
