Monday, May 28, 2012

vencer 3 telas e a nuvem

Untitled Page
The Microsoft Push Notification Service in Windows Phone offers third-party developers a resilient, dedicated, and persistent channel to send data to a Windows Phone application from a web service in a power-efficient way. 


The following diagram shows how your client application running on the phone can request a push notification URI from the Push client service (1). The Push client service then negotiates with the Microsoft Push Notification Service (MPNS) and returns a notification URI to your client application (2 and 3). Your client application can then send the URI to your cloud service (4). When your web service has information to send to your client application, it uses the URI in sending a push notification to the Microsoft Push Notification Service (5), which in turn routes the push notification to the application running on a Windows Phone device (6).

Depending on the format of the push notification and the payload attached to it, the information is delivered as raw data to the application, the application's Tile is visually updated, or a toast notification is displayed. The Microsoft Push Notification Service sends a response code to your web service after a push notification is sent indicating that the notification has been received and will be delivered to the device at the next possible opportunity. However, the Microsoft Push Notification Service does not provide an end-to-end confirmation that your push notification was delivered from your web service to the device.


Push Notifications Overview for Windows Phone


There are three types of push notifications that a web service can use when sending information to an application: toast, Tile, and raw notifications.

Toast Notifications

toast notification is displayed at the top of the screen to notify users of an event, such as a news or weather alert. The toast displays for about 10 seconds unless the user dismisses it with a flick to the right. If the user taps the toast, the application that sent the toast notification is launched.
The elements of a toast notification are:
  • Title. A boldface string that displays immediately after the application icon. This is defined as the Text1property in the XML schema.
  • Content. A non-boldface string that displays immediately after the Title. This is defined as the Text2 property in the XML schema.
  • Parameter. A parameter value that is not displayed but passed to your application if the user taps on the toast. This parameter can indicate what page the application should launch to. It can also contain name-value pairs to pass to the application. This is defined as the Param property in the XML schema.


    Tile Notifications

    Tile notification can be used to update a Tile on Start. For more information about Tile properties and how to update them, see Tiles Overview for Windows Phone. These properties on the front of a Tile can be updated using a Tile notification.



    • Title. A string indicating the title of the application. The Title must fit on a single line of text and should not be wider than the actual Tile. Approximately 15 characters will fit in the title before being truncated.
    • BackgroundImage. An image displayed on the front of the Tile. We recommend that you always have a background image on the front of the Tile.
    • Count (also known as Badge). An integer value from 1 to 99. If the value of Count is not set or it is set to 0, the circle image and value will not display in the Tile.
    These properties on the back of a Tile can be updated using a Tile notification.



    • BackTitle. A string displayed at the bottom of the back of a Tile. The BackTitle must fit on a single line of text and should not be wider than the actual Tile. Approximately 15 characters will fit in the title before being truncated.
    • BackBackgroundImage. An image displayed on the back of the Tile.
    • BackContent. A string displayed in the body of the back of a Tile. Approximately 40 characters will fit in the Tile before being truncated.


      Some additional notes on the images used for the BackgroundImage and the BackBackgroundImage properties:
      1. Tile images can be either a .jpg or .png file.
      2. Because of network variability and performance reasons, consider using local resources for Tile images.
      3. Using a .png with transparent portions to the image will allow the user’s theme color to show through.
      4. Tiles are 173 x 173 pixels. If the image you provide has different dimensions, it will be stretched to fit 173 x 173.
      5. You can use a local or remote resource for the image. If you use a local resource, it must have been installed as a part of the XAP package.
      6. If the user turns Tile notifications off, then the Tile should contain generic information. It should not contain any stale data, such as an outdated weather forecast or traffic report.
      7. https is not supported for remote images.
      8. Remote images are limited to 80 KB or less. If they are larger than 80 KB, they will not be downloaded.
      9. Remote images must download in 30 seconds or less or they will not be downloaded.
      10. If the BackgroundImage or BackBackgroundImage images fail to load for any reason, none of the other properties set in the update will be changed either.

      Raw Notifications

      You can use a raw notification to send information to your application. If your application is not currently running, the raw notification is discarded on the Microsoft Push Notification Service and is not delivered to the device.

      COMENTÁRIOS:



      * HUBS -> tudo no mesmo lugar
      * Padrões de Hardware
      * Client runtime / frameworks
      * Silverlight
       * Silverlight Toolkit
       * Windows Azure toolkit >> colocando serviços na nuvem
      * 100% FREE



No comments: