[
https://issues.apache.org/jira/browse/COUCHDB-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845349#comment-13845349
]
Alexander Shorin commented on COUCHDB-1954:
-------------------------------------------
1. This question is more interesting in next context: "Do we want to ship JS
batteries for fast prototyping and even creating rich CouchApps right out of
the box?". Having current tool set (+more coming with Fauxton) makes CouchDB
more friendly for users - just install CouchDB, erica and start creating cool
things! On other hand, for serious development these batteries are useless and
even harmful since you need to care about consistency of your app dependencies.
2. I think there is no need to apply any magic around content-type. It's easy
to change request headers from cli tools / libraries, but hard for browsers.
For instance, my firefox sends both text/html and application/json mimetypes
with Accept header - which content should be rendered at / in this case and how
I can switch between them? The only simple way that the user may asks for
specific response content type is URL like http://server/doc.html for HTML
response or http://server/doc.json for JSON one.
3. Futon uses html files for rendering database / document / etc. pages. I
think it's good idea to keep them with redirect to new URL for short migration
period.
> 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)
