On Mon, Aug 24, 2009 at 12:14 AM, Tom Sante<[email protected]> wrote: > If I'm combining thousands or millions of rows into one result set I > want my server to handle it and not some hacked together javascript on > the client side. > It's gonna be a lot faster, especially with some caching to avoid > repeating the same unnecessary work. Same reason you don't just send a > client app all docs and let it handle the view generation. The point > is, you have your database server handling the data and your client > side app handling client side stuff, and not mix things up.
That makes sense - if the data set is large enough, you may not want to do all the shipping that way. I might still build a separate query service in front of CouchDB, rather than a view server behind it, but that's just me. :) Adam -- Opscode, Inc. Adam Jacob, CTO T: (206) 508-4759 E: [email protected]
