Realities about SOAP

Design is open on several axes

  • The Switzerland of Languages
    Implementaions Java, Perl, Python, PHP, etc
  • Multiple transport protocols
    HTTP, SMTP, etc
  • Vendor independent
    Axis/IBM/Macromedia, Microsoft, Cape Clear
  • 'Swiss' Objects
    Each language has its own object implementation but their SOAP implementations should play nicely with each other
If you have closed system implemented in a particular language and you're managing both ends of the data (production and consumption), you probably don't need SOAP. I lump IBM and Macromedia with Axis since they're both packaging Axis up with their application server products.
Slide 8 of 58 Contents
  1 |   2 |   3 |   4 |   5 |   6 |   7 |   8 |   9 | 10
11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20
21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30
31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40
41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50
51 | 52 | 53 | 54 | 55 | 56 | 57 | 58
www.arachna.com > Educational Resources > Tutorials > O'Reilly Open Source Conference (2002) > Exchanging Objects and Messages With SOAP

spidaman
© 2002-2009 Ian Kallen | Copyright Notice