W3C home > Mailing lists > Public > www-ws@w3.org > June 2001

RE: webservices stack

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Sun, 24 Jun 2001 13:31:44 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D0297CD37@red-msg-07.redmond.corp.microsoft.com>
To: "Colin Adam" <colin.adam@webservices.org>, <www-ws@w3.org>

Putting the whole thing into a single stack seems somewhat confusing and
tends to cause problems representing features that span multiple
"layers" like security, QoS, etc.

Another way is to separate the concepts into groups that can interact in
various manners.  I don't know if you have seen the "three stack
diagram" which was also presented at the WS [1][2] but that is an
example of how this can be done.

A more specific comment on your layering: HTTP and friends are not
transports - they are application layer protocols that define some
services. SOAP is just a really simple application layer protocol that
defines a really simple application (the SOAP processing model) at the
core and relies on extensions for adding various services. SOAP Routing
Protocol is an example of how routing functionality can be added to SOAP

Henrik Frystyk Nielsen

[1] http://www.w3.org/2001/04/wsws-proceedings/ibm-ms-framework/img2.htm
[3] http://www.gotdotnet.com/team/xml_wsspecs/soap-rp/default.html

>I have been trying to put together a webservices stack, mainly 
>using as a template the "stack" (as reported by james snell at 
>IBM developerworks) which came out of the W3C webservices workshop.
>It reads
>1. internet - IPv4 Ipv6
>2. transport - http etc
>3. messaging - soap, xml protocol
>4. routing reliability transactions  ???
>5. workflow, discovery, registries - UDDI ebXML registry, 
>WSFL, XLANG 6. service negotiation - trading partner agreements
Received on Sunday, 24 June 2001 17:01:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:06 UTC