The Endpoint Catalog Application Block
| Retired Content |
|---|
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. |
This topic describes the Endpoint Catalog Application Block, which provides features to expose the physical addresses and other details of remote services used by smart client applications.
 Note: |
|---|
| The Disconnected Service Agent Application Block uses the Endpoint Catalog Application Block described in this guidance to manage the lists of physical addresses and other details for each connection point. |
This topic includes the following subtopics:
- Design of the Endpoint Catalog Application Block. This topic describes the way the Endpoint Catalog service in the application block is designed.
- Working with the Endpoint Catalog Application Block. This topic includes a list ofprocedures for using the application block.
- Extending the Endpoint Catalog Application Block. This topic describes how you can change the behavior of the Endpoint Catalog service to suit your own requirements.
Smart client applications must be able to make requests to remote Web services to push data updates and to retrieve external information. Almost all the Web service requests you make will be to resources that require user authentication. In other words, the requests must specify details of an account registered on the server that has the permissions required to fulfill the request.
The most common authentication method is the use of a user name and password, and optionally a domain within which the server should validate the account details (usually the domain where the account resides). The combination of the user name, password, and optionally the domain is a credential. The Endpoint Catalog Application Block stores and exposes to applications the credentials for each endpoint.
