WP7 Application Development Notes (15) push notifications

Push notification is a very important concept in WP development, because I may not need this project, but it is necessary to learn about it.

Msdn makes it very clear that there are many problems in the garden.Article.

 

Push notification

Anyone who knows about the C/S architecture knows that message transmission from the client to the server can be bidirectional. The client can actively obtain messages from the server or passively receive notifications from the server, unlike the pure B/S architecture, browsers can only actively retrieve messages from servers.

In addition, although WP mobile phones are in the C/S mode, Microsoft does not allow mobile phones to passively receive messages from servers, but server notifications cannot be implemented in this way. WP provides a proxy mechanism to implement server notifications, which is push notifications.

 

Push notification is an ECS proxy. The server cannot send messages directly to the mobile client and must send messages through the ECS proxy.

The official msdn process is as follows:

 

The process is about two steps:

1. The client obtains the notification URI from the push cloud service (mpns) and submits it to its third-party server.

 

2. a third-party server submits a notification to the push cloud service (mpns) through Uri, and pushes the notification to the mobile phone.

 

Learn more about push notifications

For a rough introduction, there is still a lot to learn about the push notification. msdn is very clear about it and I will not detail it here:

Http://msdn.microsoft.com/zh-cn/library/ff402537 (V = vs.92). aspx

 

There are many articles in the garden:

Windows Phone 7 programming practices-push notification _ Analysis of push notification implementation architecture:

Http://www.cnblogs.com/xuesong/archive/2011/04/08/2008987.html

WP7 Study Notes: Push Notification Service (the source code of the attachment is relatively intuitive)

Http://www.cnblogs.com/joetao/articles/2214482.html