OPES Callout Protocol OPES Callout Protocol SOAP Consideration - PowerPoint PPT Presentation

OPES Callout Protocol OPES Callout Protocol SOAP Consideration SOAP Consideration Abbie Barbir Barbir abbieb@nortelnetworks.com Abbie 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 Header Block ... Header Block SOAP Body Body Block ... Body Block

SOAP Efficiency or lack of it HTTP Request HTTP Body XML Syntax SOAP Envelope SOAP Body SOAP Body Block Textual Integer Sender Receiver 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