RE: HTML5ROCKS의 File API 관련 문서 검토~

안녕하세요. 이상욱 과장님.

지원해 주셔서 감사합니다~

 

1월 회의 또는 2월 회의에 발표 slot을 드릴 수 있을 것 같습니다^^

결정되는데로 알려드리겠습니다.

 

즐거운 한주되세요~

 

이원석 드림.

 

From: 이상욱[App 개발 플랫폼팀] [mailto:woogi.lee@kt.com] 
Sent: Thursday, December 15, 2011 6:25 PM
To: Wonsuk Lee
Subject: RE: HTML5ROCKS의 File API 관련 문서 검토~

 

안녕하세요 이원석 의장님

 

제가 3번 해볼께요!

 

감사합니다.

 

http://massmail.kt.com/NameCardImage/NameCardFiles/201111/b78a4eaa-07e0-
48cc-8382-402d0d55c507.png

 

From: Wonsuk Lee [mailto:wonsuk11.lee@samsung.com] 
Sent: Wednesday, December 14, 2011 7:14 PM
To: public-html-ig-ko@w3.org
Subject: HTML5ROCKS의 File API 관련 문서 검토~

 

안녕하세요. 삼성전자의 이원석입니다.

아래와 같이 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: wonsuk11.lee@samsung.com

http://www.wonsuk73.com/, twitter: @wonsuk73

-----------------------------------------

Inspire the World, Create the Future !!!

=========================================

 

 

이 메일은 지정된 수취인만을 위해 작성되었으며, 중요한 정보나 저작권을
포함하고 있을 수 있습니다. 어떠한 권한 없이, 본 문서에 포함된 정보의 전부
또는 일부를 무단으로 제3자에게 공개, 배포, 복사 또는 사용하는 것을 엄격히
금지합니다. 만약, 본 메일이 잘못 전송된 경우, 발신인 또는 당사에
알려주시고, 본 메일을 즉시 삭제하여 주시기 바랍니다. 
This E-mail may contain confidential information and/or copyright material.
This email is intended for the use of the addressee only. If you receive
this email by mistake, please either delete it without reproducing,
distributing or retaining copies thereof or notify the sender immediately.