Tuesday, February 17, 2004

The most important concept in SOA. Read this on Steve Maine's blog: I’ve said many times that open content is one of the hallmark characteristics of the service-oriented model. In fact, if someone held a gun to my head and demanded to know what the most important concept in SOA was (this happened to me just last week),  I would answer “open content” because it underlies so many other concepts in SOA. I think of the extensibility-via-single-complex-parameter pattern as a way of bringing the open content model to service signatures. I agree, though the close runner up (by a nose) is open implementation. I just coined the term to describe how SOA enables application-level content and process (aka protocols) to be bound to almost any implementation-level mechanisms via infosets and SOAP bindings. The rest of his entry is well worth a read. He also has a good entry on the pipeline architecture of Indigo. 2:50:34 PM

A nice comparison of HTTP (REST) and SOAP. Saw this on Mike Deem's blog: I think the SOAP extensibility model is an improvement over HTTP's. SOAP's extensibility model allows for application protocols to be layered on top of SOAP in clean, composeable, and well defined ways. In effect, SOAP is an application protocol platform. Though I might quibble with the words "layered on top of" instead of "woven into" and "platform" instead of "architecture" or "framework", Mike definitely gets it. The whole entry is worth a read. 1:09:34 PM