XML-RPC on Messaging Transports Other Than HTTP Talk Delivered at SOAP IETF BOF Meeting January Frank DeRose TIBCO Software, Inc Porter Drive Palo Alto, CA

1. POST /StockQuote HTTP/ Host: 3. Content-Type: text/xml 4. Content-Length: nnnn 5. SOAPMethodName: Some-Namespace-URI#GetLastTradePrice DIS HTTP Header (lines 1-5) XML-RPC Payload (lines 6-12) SOAP Request

SMTP TIBCO/Rendezvous IBM MQSeries MSMQ Other Transports Besides HTTP

Advantages of Using HTTP as a Transport HTTP is ubiquitous HTTP penetrates firewalls

Disadvantages of Using HTTP as a Transport HTTP is a synchronous, request/reply protocol HTTP is a point-to-point protocol

Communication Paradigms Supported by TIBCO 1-to-1 synchronous/asynchronous request-reply 1-to-many synchronous/asynchronous request-reply Publish/subscribe

Smart Proxy COM InterfaceInterceptorDocument Object Serialize to XML Payload Transport (Publish) TIB/Rendezvous The Information Bus

TIB/Rendezvous The Information Bus Transport (Listen) Parse XML Payload Document Object StackInvoke Service/Stub Coclass impl