OPES Callout Protocol SOAP Consideration - IETF

hungryhorsecabinΛογισμικό & κατασκευή λογ/κού

14 Δεκ 2013 (πριν από 3 χρόνια και 7 μήνες)

80 εμφανίσεις

OPES Callout Protocol
OPES Callout Protocol
SOAP Consideration
SOAP Consideration
Abbie
Abbie
Barbir
Barbir
abbieb@nortelnetworks.com
abbieb@nortelnetworks.com
Nortel Networks
Nortel Networks
Purpose
• To discuss the feasibility of
using SOAP as an OPES
Callout protocol
• Get a feedback on how SOAP is
viewed in general
SOAP as OPES Callout Protocol
• SOAP 1.1: Simple Object Access Protocol
• SOAP 1.2: Is not an acronym anymore
Features
• A “wrapper” protocol
– Data is placed in
• header blocks (Control) and
• body blocks
• Written in XML
• Independent of the wrapped data
• Independent of the transport protocol
– Transport is handled by another mechanism
• HTTP 1.1 binding is specified
• A uni-directional message exchange paradigm
Message Anatomy
SOAP Envelope
SOAP Header
SOAP Body
Header Block
Header Block
...
Body Block
Body Block
...
SOAP Efficiency or lack of it
Sender
Receiver
HTTP Request
HTTP Body
XML Syntax
SOAP Envelope
SOAP Body
SOAP Body Block
Textual Integer
0x0b66
Then Why Consider SOAP
• It all depends on deployment and what we mean by a
service in an OPES environment
• Can still design an efficient Callout Protocol using SOAP
– Fixed parse tree
– Slow Path anyway ? Is it?
• Can have access to any published service
• Facilities for Security
• Privacy
• Policy exchange
• Extensible in theory
• Why do we need another service oriented protocol
Q&A