You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "jean honlet (JIRA)" <ji...@apache.org> on 2012/11/26 15:40:58 UTC

[jira] [Updated] (COUCHDB-1611) Create a wizard in Futon to "create and replicate" a database

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

jean honlet updated COUCHDB-1611:
---------------------------------

    Description: 
Here is my Use Case:
- I have an online server, with a complete application
- Some of my user have a very bad bandwith to it
- If they had a locally configured couchdb, with only a replication to the main server, they would be very very happy
- They are not informatician, and setting up the replication would be far too much complex for them

-> I would like them to 
1/ install couchdb on their computer (wizard is easy)
2/ open my application in the online server
3/ click on a link in the online application, that would open a page in their local futon/couchdb application (this is the page I would like to have)
4/ the wizard would ask them: "do you want to have a local copy of this application url-blablabla" on your local computer
5/ the wizard create the database, ask for credentials, replicate from the online server and (nice to have) propose a bookmark to the user
6/ the final user have a offline copy of the application
7/ somewhere in the future, the user replicate back to main server (done by the application itself)

All this is not feasible by the application, due to "same-origin policy" restrictions... While letting the user clicking on the link to the wizard would avoid that restriction...

  was:
Here is my Use Case:
- I have an online server, with a complete application
- Some of my user have a very bad bandwith to it
- If they had a locally configured couchdb, with only a replication to the main server, they would be very very happy
- They are not informatician, and setting up the replication would be far too much complex for them

-> I would like them to 
1/ install couchdb on their computer
2/ open my application in the online server
3/ click on a link in the online application, that would open a page in their local futon/couchdb application
4/ the wizard would ask them: "do you want to have a local copy of this application url-blablabla" on your local computer
5/ the wizard create the database, ask for credentials, replicate from the online server and (nice to have) propose a bookmark to the user
6/ the final user have a offline copy of the application
7/ somewhere in the future, the user replicate back to main server (done by the application itself)

All this is not feasible by the application, due to "same-origin policy" restrictions... While letting the user clicking on the link to the wizard would avoid that restriction...

    
> Create a wizard in Futon to "create and replicate" a database
> -------------------------------------------------------------
>
>                 Key: COUCHDB-1611
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1611
>             Project: CouchDB
>          Issue Type: Wish
>          Components: Futon
>            Reporter: jean honlet
>              Labels: friendlyness
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Here is my Use Case:
> - I have an online server, with a complete application
> - Some of my user have a very bad bandwith to it
> - If they had a locally configured couchdb, with only a replication to the main server, they would be very very happy
> - They are not informatician, and setting up the replication would be far too much complex for them
> -> I would like them to 
> 1/ install couchdb on their computer (wizard is easy)
> 2/ open my application in the online server
> 3/ click on a link in the online application, that would open a page in their local futon/couchdb application (this is the page I would like to have)
> 4/ the wizard would ask them: "do you want to have a local copy of this application url-blablabla" on your local computer
> 5/ the wizard create the database, ask for credentials, replicate from the online server and (nice to have) propose a bookmark to the user
> 6/ the final user have a offline copy of the application
> 7/ somewhere in the future, the user replicate back to main server (done by the application itself)
> All this is not feasible by the application, due to "same-origin policy" restrictions... While letting the user clicking on the link to the wizard would avoid that restriction...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira