[ 
https://issues.apache.org/jira/browse/COUCHDB-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845372#comment-13845372
 ] 

Benoit Chesneau commented on COUCHDB-1954:
------------------------------------------

about the 

1. I am not sure/. Imo if we go to a major release, we could return a 404 pages 
describing where to find such script. Eventually I could add in erica a macro 
that replace such links.

Slightly off-topic but I disagree with [~kxepal] here. Erica can and will be 
used for more. Providing its own way to extend, inherit, plug app. Doing it 
differently from a simple dependency system that's all. But he's right one one 
point. AT the beginning and its simples form erica/couchapp are just tool to 
create and edit docs/ddoc from the file system.

2. What about simply put the HTTP API to `/couchdb` and the UI to `/ui` or `/` 
. So you keep the API separated from any extensions you can add later or 
sooner. I would keep the `/` alone so e can finally add this CAPABILITY system 
we talk sometimes ago. (a way to discover links, installed resources, version 
of the API supported) ... Also I would start to version the API.

3. Maybe we could have a way to redirect the obvious and return a detailled 404 
for the others?

> Clarify Futon/Fauxton transition
> --------------------------------
>
>                 Key: COUCHDB-1954
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1954
>             Project: CouchDB
>          Issue Type: Task
>          Components: Futon
>            Reporter: Jan Lehnardt
>
> At some point Fauxton will replace Futon. There are a few questions that we 
> should clarify before we get there:
> 1. what happens to resources like jquery.js and jquery.couch.js that are 
> currently in well-known places where CouchApps depend on them?
> 2. there are several other tickets regarding serving a human readable HTML 
> page on `/` if the client is clearly a browser. (so people don’t have to type 
> the `/_utils` manually, how does that play into rolling out Fauxton?
> 3. cool URLs don’t change: what happens to links into Futon that no longer 
> work in Fauxton that might be coming in from the docs and other tutorials, 
> including people’s in-house documentation?



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to