Flow 10: Sending Separate Delivery Content
4/8/2010
When using the FDRM API to attach content to a message, the FDRM engine passes the content to the calling application. The content passed to the calling application is in the original Separate Delivery content format, such as OMA DRM Content Format (DCF), and ready for sending. The original Separate Delivery content is wrapped appropriately in the MIME message if required.
The following illustration shows an example UI flow using a MMS picker.
.gif "Bb446752.b6e95bd8-34e5-4cd8-b97c-a8a2eace102a(en-us,MSDN.10).gif")
The following table shows the image set associated with each screen.
| Screen | Image set | Description |
|---|---|---|
Screen 3 |
Recipient will need to purchase rights (FDRM engine). |
|
Screen 4 |
MMS previewing page |
In the example shown, the FDRM-protected content will have valid time-based rights. If the user wants to preview the image or sound attached to the MMS message, valid rights are required. See the previous UI flow illustrations to see user interaction examples. |
See Also
Concepts
Recommended UI Provided by the FDRM Engine