Re: Asynchronous callbacks + www-ws

Mark,

I'm probably missing something here: the technique being discussed in the
message you refer to seems to me to be applicable if one resource (reachable
through a URL) is subscribing to messages from another resource (also
reachable through a URL). Is this correct? What if the subscriber is an
application -- is there some way to make this technique work in that case?

Thanks,

Steve
sgollery@cadrc.calpoly.edu

----- Original Message -----
From: "Mark Baker" <distobj@acm.org>
To: "Arun swaran Jagatheesan" <arun@sdsc.edu>
Cc: "Steven Gollery" <sgollery@cadrc.calpoly.edu>; <www-ws@w3.org>
Sent: Thursday, January 24, 2002 2:37 PM
Subject: Re: Asynchronous callbacks + www-ws


> > On the same lines of the previous discussion..
> >
> > Is there a standard/recommendation for asynchronous callbacks on this
> > space? - Or is it left to the individual (business) processes to evolve
> > their own standard for asynchronous callbacks and status monitoring for
> > long-run services.
>
> There's no standard yet, but some of us REST nuts have been talking
> about this recently on rest-discuss;
>
> http://groups.yahoo.com/group/rest-discuss/message/38
>
> BTW, no, I won't be following up on questions that ask why this
> doesn't use SOAP.  And yes, I do consider it a web service. 8-)
>
> MB
> --
> Mark Baker, Chief Science Officer, Planetfred, Inc.
> Ottawa, Ontario, CANADA.      mbaker@planetfred.com
> http://www.markbaker.ca   http://www.planetfred.com
>
>

Received on Friday, 25 January 2002 14:52:11 UTC