XMLRPC

1
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 fra
nkd_at_tibco.com
2
SOAP Request
1. POST /StockQuote HTTP/1.1 2. Host
www.stockquoteserver.com 3. Content-Type
text/xml 4. Content-Length nnnn 5.
SOAPMethodName Some-Namespace-URIGetLastTradePri
ce 6. ltSOAPEnvelope xmlnsSOAP"urnschemas-xmls
oap-orgsoap.v1"gt 7. ltSOAPBodygt 8.
ltmGetLastTradePrice xmlnsm"Some-Namespace-URI"gt
9. ltsymbolgtDISlt/symbolgt 10.
lt/mGetLastTradePricegt 11. lt/SOAPBodygt 12.
lt/SOAPEnvelopegt

• HTTP Header (lines 1-5)
• XML-RPC Payload (lines 6-12)

3
Other Transports Besides HTTP

• SMTP
• TIBCO/Rendezvous
• IBM MQSeries
• MSMQ

4
Advantages of Using HTTP as a Transport

• HTTP is ubiquitous
• HTTP penetrates firewalls

5
Disadvantages of Using HTTP as a Transport

• HTTP is a synchronous, request/reply protocol
• HTTP is a point-to-point protocol

6
Communication Paradigms Supported by TIBCO

• 1-to-1 synchronous/asynchronous request-reply
• 1-to-many synchronous/asynchronous request-reply
• Publish/subscribe

7
Smart Proxy
COM Interface
Interceptor
Document Object
Serialize to XML Payload
Transport (Publish)
TIB/Rendezvous The Information Bus
8
Service/Stub
Transport (Listen)
Parse XML Payload
Document Object
Stack
Invoke
Coclass impl
TIB/Rendezvous The Information Bus