On Tue, Jan 13, 2009 at 12:21 PM, Bradford Winfrey <bradswinf...@yahoo.com>wrote:
> Render seems to provide a nice, clear definition for taking data (from a > view view) and transforming (rendering) that data into something more > useful. > > Brad It also makes sense when taking data (from a doc) and transforming -- but I understand the concern about differentiating between a doc and a view. From a user perspective, depending on what you're rendering you'll have a different set query params to pass in (startkey/endkey makes no sense on render_doc). Something like _render_doc or _render_view would work nicely for me (I just want the feature -- I don't care too much of the name). But if most people want just one name, wouldn't there already be enough data in the url itself to be demonstrative of the context that you're rendering in? I imagine that... /db/_render/mydesign/myview ...could be ambiguous against... /db/_render/mydoc/mydesign/myview To break this ambiguity you could require a full path to design doc so it'd be: /db/_render/<doc_id>/<view> ...or... /db/_render/_design/mydesign/myview ...and the same for docs, essentially... /db/_render/mydoc/mydesign/myview Would this satisfy all cases?
