canmove, Confirmed users
725
edits
WebAPI/WebMMS: Difference between revisions
→Overview
No edit summary |
|||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
On the surface, MMS messages are very similar to multipart HTML emails. One part is responsible for the layout of the message, though MMS uses SMIL rather than HTML. The other parts are attachments, such as text, picture, video, and sound files. Much like in multipart | On the surface, MMS messages are very similar to multipart HTML emails. One part is responsible for the layout of the message, though MMS uses SMIL rather than HTML. The other parts are attachments, such as text, picture, video, and sound files. Much like in multipart emails, the attachments have "file names" and are referred to by those from the presentation part. | ||
The API proposal below exposes the SMIL document as a DOM tree and the attachments as Blobs (or, rather, an extension thereof, akin to how File is an extension of Blob). On a User Agent capable of rendring SMIL, the web application may simply render the DOM right away. On other User Agents, it may use XSLT or some other method to convert SMIL to HTML. | |||
To read the attachments, the web application may use the FileReader API. XXX TODO explain uri attribute; might be useful as a general blob feature, e.g. gallery storing pix in indexedDB, etc. | |||
= API = | = API = | ||