== Framework Issues ==
* '''Cloud Storage Account management and Authentication'''
* '''Data cache/buffering'''
** '''Meta Cache''' - Each file has its meta data like mdate, cdate, size, etc. Meta Cache should store any meta information for each file or directory in order to avoid network transaction to retrieve a known information.
** '''Data Cache''' - Meta Cache talks about a file’s attribute, and Data Cache is for a file content. Data Cache should store a file content requested by user for each file in order to avoid network transaction to retrieve a partial file content as a block.
** '''Cache Policy''' - Cache store entry can be flexible to adjust for different requirement, i.e. storage size. Any new request can replace one existed entry if the maximum entry is exceeded. ‘existed entry’ has not been well-defined yet, and it depends on user story. Cache policy can be aggressive to prefetch file content or meta, so the response time for each request can be improved.
* '''Offline support''' - Any requested file content/meta will be stored in cache store, so the cache store is a subset of cloud storage. Cache system still can provide cached file content from cache store even no network connection. Considering error handling for new data/meta request is important in the case of no network connection.
* '''Security issues'''
=== Issue Study ===
[https://docs.google.com/presentation/d/1gB41Z6uQQO9C51Ns2aAm2A7vJox0AYt5tz2vyDC0xuo/edit#slide=id.p Cache Architecture study]
= Related Use cases =
== Play media files saved on cloud ==
