• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

XoH vs Soap Web Services

Ranch Hand
Posts: 211
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Ranchers,

I have recently been exposed to a dilemma of making a choice between Xml over Http and Soap Web Services to implement a solution and it made me wonder about the factors which would influence an architect's choice favoring one over the other.

I considered the following to begin with -

1. Support of tooling (Soap toolkits are readily available and hence rapid development can be ensured)
2. Simplicity of use /learning curve (XOH would win hands down on this one)
3. Message Size (typically the payload size of an XOH message would be smaller)
4. Client platform support for Soap (Some clients express reluctance in using soap toolkits, here XOH is a good option)
5. Flexibility (Soap offfers much more flexibility because it accounts for intermediaries, XOH is more of a Point to Point solution)

I am hoping to have more inputs from the group...anyone?

    Bookmark Topic Watch Topic
  • New Topic