RE: [ebxml-msg] Newly released specs from Microsoft

[David Smiley <dsmiley@mercator.com>]

Doug,

I'm just starting to read the spec, but there is a mention early on that
routing can be discovered dynamically. I'm sure some  on this list will be
able to digest this for our better understanding.

David

-----Original Message-----
From: Doug Bunting [mailto:dougb62@yahoo.com]
Sent: Tuesday, October 23, 2001 1:19 PM
To: ebxml-msg@lists.oasis-open.org
Subject: Re: [ebxml-msg] Newly released specs from Microsoft


Interesting, the assortment of specifications makes it seem that mSoft has
chosen to ignore both OASIS and W3C efforts in a number of areas.  The
overview for WS-routing (previously called SOAP-RP) makes it clear all nodes
on a path must be known to everyone else -- likely not a common case in
e-business though it might be worthwhile in the general "web services"
space.  Source routing was something we explicitly avoided in ebXML-msg.

thanx to David,
    doug
Sun Microsystems, Inc.

----- Original Message -----
From: "David Smiley" <dsmiley@mercator.com>
To: <ebxml-msg@lists.oasis-open.org>
Sent: Tuesday, 23 October 2001 09:54
Subject: [ebxml-msg] Newly released specs from Microsoft


One of them involves the routing of SOAP messages using intermediaries.
Check it out at

http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid
=28000442

Use the menu on the left and navigate to:
XML and Web Services
   Web Services Specifications
      Global XML Web Services

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>