QMHCloudIntegration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
AutoSpider (talk | contribs) (Add "cleanup" tag) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
[[Category:QtEcosystemTeamTasklist]] | [[Category:QtEcosystemTeamTasklist]] | ||
| Line 5: | Line 7: | ||
==== 2012-04-20 ==== | ==== 2012-04-20 ==== | ||
First draft version is implemented. Dropbox is used as the file hosting service. It has the following limitations: | First draft version is implemented. Dropbox is used as the file hosting service. It has the following limitations: | ||
* The synchronisation is only one way, from the server to the client | |||
* Only files in the sandbox folder (Apps/qtmediahub) are synchronised, no subdirectories are included | |||
* Only files that don't exist on the (local) client are downloaded (media files content usually doesn't change, but playlists for instance) | |||
* Only four additional users are allowed access (unless the app has production status granted by Dropbox) | |||
* Each time "Dropbox" is selected from the mediahub menu a new session is initiated, i.e. user has to enter credentials (otherwise there would be not much to show - having only a daemon in the background wouldn't allow us to use the buzzword "Cloud" easily ;-) | |||
Latest revision as of 16:21, 3 March 2015
| This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
Logbook
2012-04-20
First draft version is implemented. Dropbox is used as the file hosting service. It has the following limitations:
- The synchronisation is only one way, from the server to the client
- Only files in the sandbox folder (Apps/qtmediahub) are synchronised, no subdirectories are included
- Only files that don't exist on the (local) client are downloaded (media files content usually doesn't change, but playlists for instance)
- Only four additional users are allowed access (unless the app has production status granted by Dropbox)
- Each time "Dropbox" is selected from the mediahub menu a new session is initiated, i.e. user has to enter credentials (otherwise there would be not much to show - having only a daemon in the background wouldn't allow us to use the buzzword "Cloud" easily ;-)