- From: Wonsuk Lee <wonsuk11.lee@samsung.com>
- Date: Wed, 14 Dec 2011 19:14:21 +0900
- To: public-html-ig-ko@w3.org
- Message-id: <01ba01ccba49$25b0bb60$71123220$%lee@samsung.com>
¾È³çÇϼ¼¿ä. »ï¼ºÀüÀÚÀÇ ÀÌ¿ø¼®ÀÔ´Ï´Ù. ¾Æ·¡¿Í °°ÀÌ HTML5ROCKS¿¡ ¿Ã¶ó¿Â File API °ü·Ã ¹®¼µéÀ» °ËÅäÇØ º¸¸é ÁÁÀ» °Í °°¾Æ¼ ¸ÞÀÏ º¸³À´Ï´Ù. 1. Reading local files in JavaScript [1] 2. Exploring the FileSystem APIs [2] 3. The Synchronous FileSystem API for Workers [3] [2]¸¦ º¸¸é File API È°¿ëÀÌ ÇÊ¿äÇÑ Use Case´Â ¾Æ·¡¿Í °°½À´Ï´Ù. ¾ÆÁÖ À¯¿ëÇÑ API ÀÔ´Ï´Ù~ ;) °¢ ¹®¼¸¦ KIG ȸÀǶ§ ¼Ò°³ÇØ ÁÖ½Ç Volunteer¸¦ ã½À´Ï´Ù~ ¹Ù·Î Áö¿øÇØÁÖ¼¼¿ä~^^ Âü°í·Î ¹ßÇ¥´Â 2012³â ù¹ø° ȸÀÇ°¡ µÉ °Í °°½À´Ï´Ù~ ;) 1. Persistent uploader * When a file or directory is selected for upload, it copies the files into a local sandbox and uploads a chunk at a time. * Uploads can be restarted after browser crashes, network interruptions, etc. 2. Video game, music, or other app with lots of media assets * It downloads one or several large tarballs, and expands them locally into a directory structure. * The same download works on any operating system. * It can manage prefetching just the next-to-be-needed assets in the background, so going to the next game level or activating a new feature doesn't require waiting for a download. * It uses those assets directly from its local cache, by direct file reads or by handing local URIs to image or video tags, WebGL asset loaders, etc. * The files may be of arbitrary binary format. * On the server side, a compressed tarball will often be much smaller than a collection of separately-compressed files. Also, 1 tarball instead of 1000 little files will involve fewer seeks, all else being equal. 3. Audio/Photo editor with offline access or local cache for speed * The data blobs are potentially quite large, and are read-write. * It may want to do partial writes to files (ovewriting just the ID3/EXIF tags, for example). * The ability to organize project files by creating directories would be useful. * Edited files should be accessable by client-side applications [iTunes, Picasa]. 4. Offline video viewer * It downloads large files (>1GB) for later viewing. * It needs efficient seek + streaming. * It must be able to hand a URI to the video tag. * It should enable access to partly-downloaded files e.g. to let you watch the first episode of the DVD even if your download didn't complete before you got on the plane. * It should be able to pull a single episode out of the middle of a download and give just that to the video tag. 5. Offline Web Mail Client * Downloads attachments and stores them locally. * Caches user-selected attachments for later upload. * Needs to be able to refer to cached attachments and image thumbnails for display and upload. * Should be able to trigger the UA's download manager just as if talking to a server. * Should be able to upload an email with attachments as a multipart post, rather than sending a file at a time in an XHR. [1] http://www.html5rocks.com/en/tutorials/file/dndfiles/ [2] http://www.html5rocks.com/en/tutorials/file/filesystem/ [3] http://www.html5rocks.com/en/tutorials/file/filesystem-sync/ ÀÌ¿ø¼® µå¸². ========================================= ÀÌ ¿ø ¼® (Wonsuk, Lee) / Senior Engineer, Ph.D SAMSUNG ELECTRONICS Co., LTD. (ß²àøï³í) Mobile: +82-10-5800-3997 E-mail: <mailto:wonsuk11.lee@samsung.com> wonsuk11.lee@samsung.com <http://www.wonsuk73.com/> http://www.wonsuk73.com/, twitter: @wonsuk73 ----------------------------------------- Inspire the World, Create the Future !!! =========================================
Received on Wednesday, 14 December 2011 10:14:54 UTC