W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2003

RE: concatenating web services

From: Don Box <dbox@microsoft.com>
Date: Mon, 10 Feb 2003 06:50:42 -0800
Message-ID: <57EF69AF56D92148984EDA3174082945040F9932@RED-MSG-10.redmond.corp.microsoft.com>
To: "Anne Thomas Manes" <anne@manes.net>, "Rand Anderson" <randerson@macgregor.ws>, <xml-dist-app@w3.org>

> -----Original Message-----
> From: Anne Thomas Manes [mailto:anne@manes.net]
> Sent: Thursday, January 16, 2003 1:36 PM
> To: Rand Anderson; xml-dist-app@w3.org
> 
> I don't think that web service concatenation is an intended
application
> for
> WS-Routing. WS-Routing defines a mechanism to route a message through
a
> series of SOAP intermediaries on its way to the ultimate receiver. The
> original question involved concatenating two ultimate receivers.

Your analysis of WS-Routing is spot on. That stated, I've seen people
use WS-Routing (or home-grown variations) to do some pretty twisted
things. SOAP is pretty vague about what a SOAP intermediary can do to a
message before relaying it to the next SOAP node. 

One feature of WS-Routing that would be useful in this scenario is the
ability to do transport-independent async messaging. If one crafted the
message schemas correctly, getting the first service to send a message
to the second one wouldn't be terribly hard. 

> The new W3C WS Choreography Working Group proposes to define a
language
> which would allow you to create a composite web service that would
> coordinate this type of process. The announcement for the group only
came
> out yesterday, so they haven't delivered very much yet. You might look
at
> WSCI (http://www.w3.org/TR/wsci/).

I think a simple XSLT (or equivalent) would solve this guy's problem. 

> You also might look at Collaxa
(http://www.collaxa.com/home.index.jsp). I
> think they can do something like this. But you still have to create a
new
> service that coordinates the concatenation.
> 
> Anne
> 
> > -----Original Message-----
> > From: xml-dist-app-request@w3.org
[mailto:xml-dist-app-request@w3.org]On
> > Behalf Of Rand Anderson
> > Sent: Thursday, January 16, 2003 2:38 PM
> > To: xml-dist-app@w3.org
> > Subject: RE: concatenating web services
> >
> >
> >
> > You may want to take a look at the WS-Routing protocol
> > (http://www.google.com/search?sourceid=navclient&q=ws%2Drouting).
> >
> > HTH,
> > Rand
> >
> > > -----Original Message-----
> > > From: Vix [mailto:vixcc@yahoo.com]
> > > Sent: Thursday, January 16, 2003 2:05 PM
> > > To: Sudhir Agarwal; xml-dist-app@w3.org
> > > Subject: Re: concatenating web services
> > >
> > >
> > >
> > > > i would like to know, whether it is possible to pipe the
> > > output of one
> > > > web services to the input of the other web service.
> > > ...
> > > > i want to avoid that the client c gets all the temperature
> > > data from
> > > > ws1 which it then sends to sw2 which calculates the average
> > > and sends
> > > > the answer to c. i would rather like to tell ws1 somehow
> > > (how? that is
> > > > actually my question) to send its output (list of
> > > temperatures) to ws2
> > > > and not to c. ws2 must be able interpret it as its input
> > > and must know
> > > > that it should send its output
> > > > (average) to c and not to ws1.
> > >
> > >
> > > I don't know of any existing possibility.
> > > However, I would be really careful with this if it exists.
> > > This is simply because lots of security issues might be raised
there.
> > >
> > > Please let me know if any such possibility exists.
> > >
> > > Best regards,
> > >
> > > Victor
> > >
> > >
> > >
> > > =====
> > > _,.<~=`^`=~>.,_,.<~=`^`=~>.,_,.<~=`^`=~>.,
> > > ------> tAke a bReak! gEt eNtertained!
> > > ------> http://www.sallini.com/
> > > ^`=~>.,_,.<~=`^`=~>.,_,.<~=`^
> > > -> http://netdesignplus.net/
> > > -> It works... It Pays...
> > > _,.<~=`^`=~>.,_,.<~=
> > >
> > > __________________________________________________
> > > Do you Yahoo!?
> > > Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> > http://mailplus.yahoo.com
> >
Received on Monday, 10 February 2003 09:51:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:13 GMT