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

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 page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

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.

Ff648309.note(en-us,PandP.10).gifNote:
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:

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.

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