Close
  • Latest News
  • Big Data and Analytics
  • Cloud
  • Networking
  • Cybersecurity
  • Applications
  • IT Management
  • Storage
  • Sponsored
  • Mobile
  • Small Business
  • Development
  • Database
  • Servers
  • Android
  • Apple
  • Innovation
  • Blogs
  • PC Hardware
  • Reviews
  • Search Engines
  • Virtualization
Read Down
Sign in
Close
Welcome!Log into your account
Forgot your password?
Read Down
Password recovery
Recover your password
Close
Search
Logo
Logo
  • Latest News
  • Big Data and Analytics
  • Cloud
  • Networking
  • Cybersecurity
  • Applications
  • IT Management
  • Storage
  • Sponsored
  • Mobile
  • Small Business
  • Development
  • Database
  • Servers
  • Android
  • Apple
  • Innovation
  • Blogs
  • PC Hardware
  • Reviews
  • Search Engines
  • Virtualization
More
    Home Applications
    • Applications
    • Development
    • IT Management

    Amazon, eBay Get Attached to SOAP Messaging Spec

    By
    Jason Levitt
    -
    September 13, 2004
    Share
    Facebook
    Twitter
    Linkedin

      It seems inevitable that when you put Microsoft, IBM and Sun (and HP and TIBCO and BEA, etc.) in the same room over and over again, youll end up with some porky specifications. Sure enough, the Simple Object Access Protocol (along with its numerous related appendages) has been getting bigger and more confusing every year.

      All of those evolving specifications can be conveniently ignored if you have the luxury of defining the terms of the transaction. For example, if my fictional company, Monolithic Entity Inc., wants to exchange data with its suppliers, it can define its own terms. Maybe well use our own home-brewed XML with compression and just bypass SOAP entirely. Or, perhaps well use a variant of SOAP 1.0 that relies mostly on attachments being sent out-of-band (not in the SOAP package).

      This is exactly the way many businesses have handled their Web services transactions—using the tools available in their own way and not waiting (perhaps years) for the committee-driven standards to make their way into draft form.

      But the stakes are different when you start creating public-facing Web services. Both eBay and Amazon, which are at the forefront of large-scale Web services deployments, have realized this. If you want 20,000-plus developers to play with your Web services, you need standards that interoperate. Your developers may be using Java or .Net or Perl or Python, and there may be multiple SOAP tool kits available for each language. Suddenly, committee-driven standards dont seem so bad—provided they interoperate.

      In turn, those 20,000 developers may bring in 100,000 SOAP requests an hour (or minute) with their applications. Performance and scalability arent issues that can be handled ad hoc in these kinds of environments.

      One hurdle that has only recently been put to rest (hopefully) is how to handle attachments with SOAP messaging. By attachments, I mean the same thing as e-mail attachments—a binary file such as a JPEG photo. Some people call these things “blobs,” or “opaque data,” but Ill just call them attachments.

      Attachments turn out to be important to both eBay and Amazon as their sellers are constantly dealing with various types of binary information and need an efficient—and interoperable—way of sending and receiving them via SOAP. But attachments have also been one of the blurriest appendages of the SOAP standard and generally have been neither efficient nor interoperable.

      Between 2000 and 2003 there were no less than three proposals to handle attachments to SOAP messages. HP and Microsoft started things off in late 2000 with the SOAP with Attachments draft, commonly referred to as “SwA.” This was a simple specification that let SOAP messages refer to out-of-band attachments that were MIME-encoded (just like e-mail attachments). But MIME (Multipurpose Internet Mail Extension) attachments are just base64-encoded, which tends to increase the attachment size by 30 percent or more. Not good.

      In 2002, Microsoft came up with WS-attachments, which replaced MIME encoding with a new compressed format called DIME (Direct Internet Message Encapsulation). DIME was quickly implemented in Microsofts tool kits, but not widely outside of Microsoft.

      In 2003, Microsoft and others proposed a new version of SwA called Proposed Infoset Addendum to SOAP Messages with Attachments. Commonly know as “PASwA,” it suggests how MIME encoding (and associated compression mechanisms) could be integrated into the SOAP messaging stream.

      The latest, and by all accounts, final salvo, came in mid-2003. The Message Transmission Optimization Mechanism, or MTOM, which was co-authored by IBM, Canon, BEA, and Microsoft, takes the better parts of most of the previous attachments specs and provides some clear guidance for interoperability. In fact, its coverage is somewhat broader (note that the title no longer refers to attachments but to “optimization”) as it allows for various transports and compression methods and allows the attachment to be contained within the SOAP packet. Importantly, the attachment is packaged as an XML infoset, which means that it can be handled as a regular XML object as opposed to something thats (possibly) non-XML compliant.

      The W3C MTOM Candidate Recommendation was published on August 26th. Microsoft is expected to drop DIME support (which they offer in their SOAP tool kit) in favor of MTOM and that effectively makes it the de facto standard.

      Three years isnt too bad for a committee-driven specification, and, to be fair, this was new territory for messaging— no one really knew the best solution. EBay and Amazon are also covering new ground with their public-facing, high-volume Web services, and that will drive more immediate demand for interoperable standards.

      Check out eWEEK.coms Web Services Center for the latest news, reviews and analysis in programming environments and developer tools.

      Jason Levitt
      Jason Levitt is a programmer, consultant, book author and web jockey. He is is a former senior technology editor for InformationWEEK. Currently, Levitt is completing an upcoming book on web services for O'Reilly and Associates.

      MOST POPULAR ARTICLES

      Cybersecurity

      Visa’s Michael Jabbara on Cybersecurity and Digital...

      James Maguire - May 17, 2022 0
      I spoke with Michael Jabbara, VP and Global Head of Fraud Services at Visa, about the cybersecurity technology used to ensure the safe transfer...
      Read more
      Cloud

      Yotascale CEO Asim Razzaq on Controlling Multicloud...

      James Maguire - May 5, 2022 0
      Asim Razzaq, CEO of Yotascale, provides guidance on understanding—and containing—the complex cost structure of multicloud computing. Among the topics we covered:  As you survey the...
      Read more
      IT Management

      Intuit’s Nhung Ho on AI for the...

      James Maguire - May 13, 2022 0
      I spoke with Nhung Ho, Vice President of AI at Intuit, about adoption of AI in the small and medium-sized business market, and how...
      Read more
      Big Data and Analytics

      GoodData CEO Roman Stanek on Business Intelligence...

      James Maguire - May 4, 2022 0
      I spoke with Roman Stanek, CEO of GoodData, about business intelligence, data as a service, and the frustration that many executives have with data...
      Read more
      Applications

      Cisco’s Thimaya Subaiya on Customer Experience in...

      James Maguire - May 10, 2022 0
      I spoke with Thimaya Subaiya, SVP and GM of Global Customer Experience at Cisco, about the factors that create good customer experience – and...
      Read more
      Logo

      eWeek has the latest technology news and analysis, buying guides, and product reviews for IT professionals and technology buyers. The site’s focus is on innovative solutions and covering in-depth technical content. eWeek stays on the cutting edge of technology news and IT trends through interviews and expert analysis. Gain insight from top innovators and thought leaders in the fields of IT, business, enterprise software, startups, and more.

      Facebook
      Linkedin
      RSS
      Twitter
      Youtube

      Advertisers

      Advertise with TechnologyAdvice on eWeek and our other IT-focused platforms.

      Advertise with Us

      Menu

      • About eWeek
      • Subscribe to our Newsletter
      • Latest News

      Our Brands

      • Privacy Policy
      • Terms
      • About
      • Contact
      • Advertise
      • Sitemap
      • California – Do Not Sell My Information

      Property of TechnologyAdvice.
      © 2021 TechnologyAdvice. All Rights Reserved

      Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.

      ×