
Subscriber and Subscription Management
Notification Services generates notifications based on subscriptions created by subscribers. These subscribers can be people or other applications. As part of developing a Notification Services application, you develop one or more interfaces so that subscribers can manage their subscriptions.
Subscriber data includes a subscriber ID and information about the subscriber's devices, such as e-mail addresses and text messaging addresses. Each subscriber can have multiple devices.
Subscriber data is stored in instance database objects. All applications hosted by an instance of Notification Services use the same subscriber data.
Subscription data specifies what application information the subscriber is interested in, such as the city for weather forecasts, and which device receives the notifications. Your application might have built-in logic to select subscriber devices based on conditional logic, such as day, time, or message importance.
Subscription data is stored in application databases. Each application has its own subscription data.
Most Notification Services applications provide an interface that subscribers can use to manage their subscriber and subscription data. This is frequently an ASP.NET application, but can be a Windows application, Web service, or any other interface you want to develop using the Notification Services subscription management objects. For more information, see Developing Subscription Management Interfaces.