Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Conclusion

On this page:Download:
Questions | More Information Download code samples
Download book as PDF

This chapter described the ways in which the Tailspin Surveys mobile client application accesses remote services; it also discussed designing services that Windows Phone can access. You have now seen a complete picture of the Tailspin Surveys mobile client application, including the application's UI, Tailspin's use of the MVVM pattern, how the application leverages services offered by the Windows Phone platform, and how it consumes services over the network.

Questions

  1. How does Tailspin pass authentication requests to the web service?
    1. Tailspin uses basic authentication with the credentials in an authorization header.
    2. Tailspin uses Window Live ID.
    3. Tailspin uses OAuth.
    4. Tailspin uses the Windows Identity Framework (WIF).
  2. What notification methods does the Microsoft Push Notification Service support?
    1. Toast notifications.
    2. Tile notifications.
    3. SMS notifications.
    4. Raw notifications.
  3. Which of the following are elements of a toast notification?
    1. A title string that displays after the application icon.
    2. A content string that displays after the title.
    3. A background image.
    4. A parameter value that is not displayed but is passed to the application if the user taps on the toast.
  4. Why does the client need to register with MPNS before it can receive notifications?
    1. Because MPNS requires clients to authenticate before it will send notifications.
    2. Because MPNS can then notify your service that the client is ready to receive notifications.
    3. Because the client must obtain a unique URI to send to your service.
    4. Because the free version of MPNS has a limit on the number of clients that can receive notifications from your service.
  5. How does Tailspin transport data between the client and the web service?
    1. Tailspin uses the Microsoft Sync Framework to handle the data transport.
    2. Tailspin uses the WCF Data Services framework.
    3. Tailspin uses data transfer objects with a WCF REST endpoint.
    4. The mobile client application uploads directly to Windows Azure BLOB storage.
  6. Why does Tailspin filter data on the server and not on the client?
    1. To minimize the amount of data moved over the network.
    2. To simplify the application.
    3. For security reasons.
    4. To minimize storage requirements on the phone.

More Information

For more information about push notifications, see "Push Notifications for Windows Phone" on MSDN.

For more information about developing websites for Windows Phone, see "Web Development for Windows Phone" on MSDN.

For more information about security for Windows Phone, see "Security for Windows Phone" on MSDN.

These and all links in this book are accessible from the book's online bibliography. You can find the bibliography on MSDN at: http://msdn.microsoft.com/en-us/library/gg490786.aspx.

Last built: May 25, 2012

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.