search

Hypertopic / LaSuli

Social annotation for qualitative analysis
https://hypertopic.org/lasuli
GNU General Public License v3.0
12 stars 4 forks source link

Service identification shouldn't be based on its implementation #15

Closed benel closed 12 years ago

benel commented 13 years ago

It should rather be based on a JSON static payload.

For example:

{"service":"Cassandre"}

Note: This payload could include other attributes too (revision, etc.).

chao commented 12 years ago

Where should we put this? Create a document with special ID? or create a list function?

benel commented 12 years ago

The simplest way to implement that would be to attach a json file to the design document and to add a rewrite rule so that its URL would be /.

benel commented 12 years ago

Erm, I forgot that Cassandre and Steatite have already a user readable representation for /. In that case, the JSON document will be sent only if the Accept header is application/json.

benel commented 12 years ago

Note: Last revisions on Cassandre are unstable... Please base your edits on e46c11e5c181edf07dc6c9ae57ff337e0d95464d.

chao commented 12 years ago

Fixed, both Cassandre and Argos are updated to provide this payload.