Beyond the Hype
  • Loosely coupled systems can work together
  • Dissimilar systems can interoperate
  • Applications don't need SOAP awareness
  • You can stop inventing proprietary protocols
  • You can bypass firewall obstacles
    wait, is that good?
If you have separate systems written in separate languages, SOAP is a good bet. For closely related related systems written in the same implementation language, it's probably not the right choice.
Slide 9 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