Your SlideShare is downloading. ×
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Web services
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Web services

160

Published on

Found this while SOAP vs REST deck while cleaning out an old hard drive...

Found this while SOAP vs REST deck while cleaning out an old hard drive...

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
160
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Application Development Web Services Episode IV: A New Hope Hans Granqvist Sr. Engineer, VIS Application Development Web Services Episode IV: A New Hope Hans Granqvist Sr. Engineer, VIS
  • 2. Web services, def. •Machine-to-machine •XML – Messaging, encoding •“Service” – Describe, discover, use •Interoperable
  • 3. History 101
  • 4. 1950-ies •Procedure calls
  • 5. 1976 •Remote Procedure Calls (RFC 707)
  • 6. 1989 •Object-oriented RPC – Brokers
  • 7. 1995-ish •XML-RPC – RPC over the internet – 2 pages – 9 data types
  • 8. Example XML-RPC POST /RPC2 HTTP/1.0 User-Agent: Curl/5.1.2 (Windows) Host: example.org Content-Type: text/xml Content-length: 162 <?xml version="1.0"?> <methodCall> <methodName>example.getStateName</methodName> <params> <param><value><i4>41</i4></value></param> </params> </methodCall>
  • 9. 1998
  • 10. SOAP •Abstract messaging framework – HTTP – Data types – Recipients – Rules & controls – Infinitely customizable
  • 11. SOAP •Content – Envelope = (Headers, Body) •Encoding – Section 5 or literal •Structure – RPC or Document-centric
  • 12. Example SOAP <SOAP-ENV:Envelope xmlns:SOAP- ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:xsi="http://www.w3.org/1999/XMLSchema- instance"> SOAP-ENV:Header . . . Meta data . . . Optional data . . . /SOAP-ENV:Header SOAP-ENV:Body w:stateName xmlns:m=http://example.com/ num xsi:type=xsd:int41/num /m:stateName /SOAP-ENV:Body /SOAP-ENV:Envelope
  • 13. Criticism •HTTP as transport •Collapsed URI •Firewalls •Patents •…Umm, okay, complexity
  • 14. • WSDL, UDDI, MTOM, BPEL4WS, WS-CDL, ASAP, WSRP • WS- – Policy, Metadataexchange, Reliability, PolicyAttachement, ReliableMessaging, Addressing, MessageDelivery, Notification, Enumeration, Trust, Coordination, SecurityPolicy, Transfer, CAF, Federation, SecureConversation, Eventing, Transactions, Security, Provisioning, Manageability, … • OASIS, W3C, WS-I, IETF • IBM, BEA, TIBCO, Microsoft, Sun, SAP, Oracle, VeriSign
  • 15. *
  • 16. REST = Architectural style
  • 17. •Not software, nor a specification – Selection of ideals – Best practices •Not magic! •The Web = REST REST
  • 18. 1. Resources • Named resources • Logical URLs • Nouns http://verisign.com/certs/04224
  • 19. 2. Representations • XML/HTML/JPG/ . . . • Interconnected, traversable ?xml version=1.0? certificate id04224/id . . . owner xlink:href= http://verisign.com/owner/1701-A/ /owner /certificate
  • 20. 3. State
  • 21. 4. HTTP • Application protocol • PUT, GET, POST, DELETE – Create, Retrieve, Update, Delete • Use of headers fundamental – Accept, Content-type . . . and many more
  • 22. Accept: text/*; text/html -- -- Content-Type: text/xml POST /test HTTP/1.1 Host: http://verisign.com Content-Type: text/xml Content-length: . . . message . . . /message Headers Content
  • 23. REST Criticism and Responses
  • 24. Security • RFC 2617 (HTTP Auth) – Extensible! • XMLDSIG and XMLENC still applicable • And so is HTTPS
  • 25. Description Discovery • UDDI R.I.P. – January 12, 2006: IBM, SAP, MSFT kill public UDDI server • WSDL 2.0
  • 26. Reliability, Tools • Web is internet scale • IDEs not necessary
  • 27. Auditing, policy, eventing… • Application issues!
  • 28. Is there a happy ending?
  • 29. SOAP vs. REST • Completeness vs. Toy-like • Pragmatism vs. Hippie ideology or • Bloated vs. Agile • Complexity vs. Simplicity • Web 1.0 vs. Web 2.0
  • 30. Conclusion •Both SOAP and REST needed – Simplicity rules •Consider REST – Side-effects •Consider security issues •WS-* momentum •Fight the good fight!
  • 31. Thank you! Q/A?
  • 32. “Web 2.0”

×