Closed
Bug 792330
Opened 12 years ago
Closed 12 years ago
B2G MMS: MMSCONF-MED-C-0{06, 07, 08, 09, 10, 12, 15, 34, 35}: Support multiple media types
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: vicamo, Assigned: ctai)
References
Details
Attachments
(2 files, 2 obsolete files)
(deleted),
patch
|
vicamo
:
review+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
Details | Diff | Splinter Review |
See OMA-TS-MMS-CONF-V1_3-20110913-A section 7, 7.1.1, and Appendix C.1.12
See OMA-ETS-MMS_CON-V1_3-20101015-C section 5.1.2.2.1, 5.1.2.2.2, 5.1.2.2.3, 5.1.2.2.4, 5.1.2.2.5, 5.1.2.2.6, 5.2.3.2.1, 5.2.3.2.2, 5.2.3.2.3, 5.2.3.2.4, 5.2.3.2.5, 5.2.3.2.6, 5.2.3.2.9
Reporter | ||
Comment 1•12 years ago
|
||
They are:
1) text/plain, encoding=us-ascii, utf-8, utf-16
2) image/jpeg
3) image/gif
4) image/vnd.wap.wbmp
5) audio/amr
6) vCard & vCalendar
But maybe we should just add as much media types as possible. Additional types to be addressed:
7) H.263 & AMR (3GP)
8) MP4
9) JFIF
Actually, I think we should just add everything listed in http://www.wapforum.org/wina/wsp-content-type.htm
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → ctai
Assignee | ||
Comment 2•12 years ago
|
||
I think we should follow the OMNA WSP Content Type Numbers which listed in http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.aspx
Because the types listed in http://www.wapforum.org/wina/wsp-content-type.htm’ are from 0x00 to 0x4B. The Content Type Numbers which listed in http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.aspx are from 0x00 to 0x5A (0x51 - 0x5A is tbd). It looks like the wsp content type listed in OMA is latest one.
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Chia-hung Tai [:ctai :ctai_mozilla :cht] from comment #2)
> I think we should follow the OMNA WSP Content Type Numbers which listed in
> http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.aspx
Thanks. Please also updates the url in the comments of WspPduHelper.jsm
Assignee | ||
Comment 4•12 years ago
|
||
Assignee | ||
Updated•12 years ago
|
Attachment #683839 -
Flags: feedback?(vyang)
Assignee | ||
Comment 5•12 years ago
|
||
Attachment #683839 -
Attachment is obsolete: true
Attachment #683839 -
Flags: feedback?(vyang)
Assignee | ||
Comment 6•12 years ago
|
||
Attachment #683846 -
Attachment is obsolete: true
Assignee | ||
Updated•12 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 7•12 years ago
|
||
Comment on attachment 683849 [details] [diff] [review]
Add all WSP content types into WSP_WELL_KNOWN_CONTENT_TYPES
Please help to review this patch.
Thanks
Attachment #683849 -
Flags: review?(vyang)
Assignee | ||
Comment 8•12 years ago
|
||
Try server log:
https://tbpl.mozilla.org/?tree=Try&rev=db17a8d8467e
Reporter | ||
Comment 9•12 years ago
|
||
Comment on attachment 683849 [details] [diff] [review]
Add all WSP content types into WSP_WELL_KNOWN_CONTENT_TYPES
Review of attachment 683849 [details] [diff] [review]:
-----------------------------------------------------------------
Great!
Attachment #683849 -
Flags: review?(vyang) → review+
Assignee | ||
Updated•12 years ago
|
Keywords: checkin-needed
Reporter | ||
Comment 10•12 years ago
|
||
Reporter | ||
Updated•12 years ago
|
Keywords: checkin-needed
Comment 11•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
Updated•12 years ago
|
Assignee | ||
Updated•12 years ago
|
blocking-b2g: --- → leo?
Assignee | ||
Comment 12•12 years ago
|
||
For mms merge to b2g18.
Updated•12 years ago
|
blocking-b2g: leo? → leo+
Assignee | ||
Comment 13•12 years ago
|
||
Comment 14•12 years ago
|
||
status-b2g18:
--- → fixed
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → wontfix
status-firefox20:
--- → fixed
Comment 15•12 years ago
|
||
The entire set of clian's pushes was backed out for multiple reasons.
https://tbpl.mozilla.org/?tree=Mozilla-B2g18&rev=a0b06192f882
1.) The tree rules are clear that you are not to land on top of bustage. At the time you pushed, both B2G Mn and B2G xpcshell had bustage from prior commits that hadn't been backed out yet.
2.) The tree rules are also clear that you are to watch your pushes for any bustage and handle them accordingly. mozilla-inbound is the ONLY tree where this rule does not apply.
3.) Even after the earlier bustage was backed out, something in one of your many pushes was causing further B2G Mn failures as shown in the log below.
https://tbpl.mozilla.org/php/getParsedLog.php?id=20424173&tree=Mozilla-B2g18
4.) This isn't cause for backout by itself, but it is also strongly preferred to not push each commit individually as our build and testing resources are limited and doing so stretches them even thinner. Please limit your number of pushes as much as possible unless you have good reason for keeping them separate.
Reporter | ||
Comment 16•12 years ago
|
||
Reporter | ||
Updated•12 years ago
|
Blocks: mms-oma-compliance
Updated•12 years ago
|
Flags: in-moztrap-
You need to log in
before you can comment on or make changes to this bug.
Description
•