RFC 4227:Using the Simple Object Access Protocol (...
RFC-Ref
Previous
|
Next
Frontpage
|
Contents
|
Keywords
Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
1. Introduction
2. BEEP Profile Identification
2.1. Profile Initialization
3. SOAP Message Packages
4. SOAP Message Patterns
4.1. One-Way Message
4.2. Request-Response Exchange
4.3. Request/N-Responses Exchange
4.4. Error Handling
5. SOAP Protocol Binding Framework Conformance
5.1. Binding Name
5.2. Base URI
5.3. Supported SOAP Message Exchange Patterns
5.4. Supported Features
5.5. MEP Operation
5.5.1. Behavior of Requesting SOAP Node
5.5.1.1. Init
5.5.1.2. Requesting
5.5.1.3. Sending+Receiving
5.5.1.4. Success and Fail
5.5.2. Behavior of Responding SOAP Node
5.5.2.1. Init
5.5.2.2. Receiving
5.5.2.3. Receiving+Sending
5.5.2.4. Success and Fail
6. URL Schemes
6.1. The soap.beep URL Scheme
6.1.1. Resolving IP/TCP Address Information
6.2. The soap.beeps URL Scheme
7. Registration Templates
7.1. SOAP Profile Feature Registration Template
8. Initial Registrations
8.1. Registration: The SOAP Profile
8.2. Registration: The soap.beep URL Scheme
8.3. Registration: The soap.beeps URL Scheme
8.4. Registration: The System (Well-Known) TCP Port Number for SOAP
9. Security Considerations
10. IANA Considerations
11. Changes from RFC 3288
12. Acknowledgements
13. References
13.1. Normative References
13.2. Informative References
14. Appendix A. SOAP with Attachments (Informative)
15. Authors' Addresses
16. Full Copyright Statement
17. Intellectual Property
18. Acknowledgement
Previous
|
Next
Frontpage
|
Contents
|
Keywords
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org
