 - An endpoint reference (EPR) is a combination of Web services (WS) elements that define the address for a resource in a Simple Object Access Protocol (SOAP) header. In this context, an endpoint is any user device connected to a network. Endpoints can include personal computers (PCs), personal digital assistants (PDAs) and specialized equipment such as inventory scanners and point-of-sale terminals.
An EPR consists of a Uniform Resource Identifier (URI), message reference parameters and data concerning the interface to be used. The EPR may also contain a set of policies relevant to the endpoint such as its intended behavior and capabilities. An EPR allows the sender to tailor a message to meet specific needs. Common examples include "reply-to" and "from" addresses that the recipient can use for authentication, response or acknowledgment of receipt.
 |
Learn more about SOAP (Simple Object Access Protocol) |
| Simple Object Access Protocol (SOAP) Tutorial: This SOAP tutorial provides insight in SOAP basics, how it compares to REST, SOAP attachments and how SOAP functions with WSDL will be covered. |
| Application servers processing SOAP requests: When an application server gets a SOAP request, what namespaces/schemas does it use to parse it? Does it rely on SOAP message data or WSDL? |
| SOAP and WSDL work together: How do you use SOAP to communicate with WSDL? (i.e web services written in java) |
| REST vs. SOAP: What are your thoughts on the whole REST vs. SOAP debate? |
| Mule architect sees REST with Atom rising, UDDI fading: Dan Diephouse, the creator of XFire and software architect at MuleSource Inc., discusses the advantages in using REST and the Atom Publishing Protocol. |
| Simple Object Access Protocol (SOAP) Tutorial: This SOAP tutorial provides insight in SOAP basics, how it compares to REST, SOAP attachments and how SOAP functions with WSDL will be covered. |
| Chapter of the week: Security and Ajax: This chapter, excerpted from Ajax in Action, discusses security-related concerns that have particular implications for Ajax. |
| Chapter of the week: XML Web services: This chapter, excerpted from Core C# and .NET, takes a look at the pluses and minues of implementing and consuming Web services in a .NET environment. |
| Chapter of the week: Introduction to Web services technologies: This chapter, excerpted from Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services, focuses on the standards that make up the Web services platform and how Web ... |
| Chapter of the week: Advanced Messaging, Metadata and Security: This chapter, excerpted from Service-Oriented Architecture: Concepts, Technology, and Design, focuses on the various WS-* extensions that govern specific areas of the SOAP messaging framework. ... |
| LAST UPDATED: |
16 May 2007
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
