couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Wertheim (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COUCHDB-2311) Decouple response from request by not having to parse id from req. URL
Date Sun, 31 Aug 2014 09:06:53 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Wertheim updated COUCHDB-2311:
-------------------------------------

    Description: 
When getting a response, I would like it to be as decoupled from the request as much as possible.

E.g. When doing a HEAD for a document. I would, in the response, without having to parse the
requested URL, know what the Id is to continue working with the response.

Solution? Include as header?

*Use case:*
You have an app that returns uniformed responses, that when applicable (targeting a specific
document), provides a {{response.Id}} property. E.g. for {{GET, POST, PUT, HEAD, DELETE}}
and so on.

In an optimal world it would be one way to extract the "_id" and in the same way and with
the same name "_id" != "id"

  was:
When getting a response, I would like it to be as decoupled from the request as much as possible.

E.g. When doing a HEAD for a document. I would, in the response, without having to parse the
requested URL, know what the Id is to continue working with the response.

Solution? Include as header?


> Decouple response from request by not having to parse id from req. URL
> ----------------------------------------------------------------------
>
>                 Key: COUCHDB-2311
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2311
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>            Reporter: Daniel Wertheim
>
> When getting a response, I would like it to be as decoupled from the request as much
as possible.
> E.g. When doing a HEAD for a document. I would, in the response, without having to parse
the requested URL, know what the Id is to continue working with the response.
> Solution? Include as header?
> *Use case:*
> You have an app that returns uniformed responses, that when applicable (targeting a specific
document), provides a {{response.Id}} property. E.g. for {{GET, POST, PUT, HEAD, DELETE}}
and so on.
> In an optimal world it would be one way to extract the "_id" and in the same way and
with the same name "_id" != "id"



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message