- From: Arun swaran Jagatheesan <arun@sdsc.edu>
- Date: Thu, 24 Jan 2002 14:08:56 -0800
- To: "Steven Gollery" <sgollery@cadrc.calpoly.edu>, <www-ws@w3.org>
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. Thanks, Arun. ---------- Dream; because, dreams lead to thoughts; thoughts lead to action, and action leads to achievement. Arun swaran Jagatheesan Mission: GriPhyN (http://www.griphyn.org) San Diego Supercomputer Center. (858)822.5452 > -----Original Message----- > From: www-ws-request@w3.org [mailto:www-ws-request@w3.org]On Behalf Of > Steven Gollery > Sent: Thursday, January 24, 2002 1:55 PM > To: www-ws@w3.org > Subject: Re: "notification" pattern for web services > > > James, > > Thanks for the tip. I just took a look at the NotificationClient in the > wstk, and I have a couple of follow-up questions (I also left these > questions on the Alphaworks wstk discussion forum). > > It looks like the NotificationClient is also a web service -- am I right > about that? Is it possible to be a subscriber without also being a web > service? > > Thanks again, > > Steve > > ----- Original Message ----- > From: "James M Snell" <jasnell@us.ibm.com> > To: "Steven Gollery" <sgollery@cadrc.calpoly.edu> > Sent: Thursday, January 24, 2002 10:23 AM > Subject: Re: "notification" pattern for web services > > > > The IBM Web Services Toolkit version 3.0 release has a sample prototype > > "Notification Service" that does simple pub/sub messaging. It is, > > however, just a first step. It is available at > > http://alphaworks.ibm.com/tech/webservicestoolkit > > > > - James M Snell/Fresno/IBM > > Web services architecture and strategy > > Internet Emerging Technologies, IBM > > 544.9035 TIE line > > 559.587.1233 Office > > 919.486.0077 Voice Mail > > jasnell@us.ibm.com > > Programming Web Services With SOAP, O'reilly & Associates, ISBN > > 0596000952 > > > > == > > Have I not commanded you? Be strong and courageous. Do not be > terrified, > > > > do not be discouraged, for the Lord your God will be with you > wherever you > > go. > > - Joshua 1:9 > > > > Sent by: www-ws-request@w3.org > > To: www-ws@w3.org > > cc: > > Subject: "notification" pattern for web services > > > > > > > > In several documents, I've seen references to providing web services > > that follow the notification (or publish/subscribe) pattern, but I've > > never seen any sample code. I can see a way to do it using socket > > connections for the notification, but obviously there are going to be > > many situations where this won't work. > > > > Does anyone know where I can find code implementing a publish/subscribe > > web service? The scenario I have in mind is: (1) the web service > > advertises that it can provide information about a given set of topics; > > (2) clients connect to the web service and subscribe to particular > > topics; (3) other clients publish information about some topic by > > sending that information to the web service; (4) the web service sends > > the information to all the clients that subscribe to that topic. This > > has to work regardless of whether the clients are behind a firewall, and > > it would also be nice if there was some way for browser-based clients to > > participate. > > > > If building a publish/subscribe system using just web services is > > impractical in the general case, I'd also be interested in other ideas > > that would play well in a system that is primarily based on web > > services. > > > > Thanks in advance, > > > > Steven Gollery > > sgollery@cadrc.calpoly.edu > > > > > > > > > > > > >
Received on Thursday, 24 January 2002 17:12:05 UTC