Do browsers allow setting of custom headers? I'm fairly certain they don't, meaning that any control of CouchDB accomplished that way would be unavailable to pure CouchApps that run in a browser. That seems like a major design limitation unless I'm missing something.
On Thu, Feb 19, 2009 at 3:19 PM, Chris Anderson <jch...@apache.org> wrote: > On Thu, Feb 19, 2009 at 2:49 PM, Noah Slater <nsla...@apache.org> wrote: > > On Thu, Feb 19, 2009 at 05:46:20PM -0500, Paul Davis wrote: > >> My only real point is that the whole issue is rather gray and we > >> should look around to see if maybe there's already a proposed header > >> of similar intent. The cache control was just me trying to make the > >> point that this is mostly just the product of slight differences in > >> interpretation. As clearly demonstrated by the length and content of > >> the thread. :D > > > > I poked around the WebDAV RFC but found nothing of note. > > > > Full-Commit clearly doesn't belong in the request body (that's where > the doc goes) and it doesn't quite fit in the resource identifier > either. > > There's not much left but the headers... > http://tools.ietf.org/html/rfc3864 doesn't look like too much trouble, > and then we'd be playing by the rules. > > > -- > Chris Anderson > http://jchris.mfdz.com >
