2. XML-RPC on Messaging Transports Other Than HTTP Talk Delivered at SOAP IETF BOF Meeting January 25 2000 Frank DeRose TIBCO Software, Inc. 3165 Porter Drive Palo Alto, CA 94303 http://www.tibco.com frankd@tibco.com

3. 1. POST /StockQuote HTTP/1.1 2. Host: www.stockquoteserver.com 3. Content-Type: text/xml 4. Content-Length: nnnn 5. SOAPMethodName: Some-Namespace-URI#GetLastTradePrice 6. 7. 8. 9. DIS 10. 11. 12. HTTP Header (lines 1-5) XML-RPC Payload (lines 6-12) SOAP Request

4. SMTP TIBCO/Rendezvous IBM MQSeries MSMQ Other Transports Besides HTTP

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

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

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

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

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