Title: Message
Joe, James,
 
As Sal mentioned, the WSDM 1.0 standard does not define start/stop operations. However, if these operations make sense for the resources you are providing manageability for, you can define them. Joe's initial comments sound like you are not sure what to do with these operations, so it is not necessary to implement them.
 
That said, start/stop can make a lot of sense for some resources: database, server, app-server, storage-system, printer, etc. For these types of resources either an industry organization or the manageability provider will define what start/stop means for the resource.
 
Kinga and Sal have already mentioned how start/stop might be applied to a resource that is a Web service. I have also implemented a solution similar to that described by Kinga. Another approach is to "undeploy" the Web service. In .NET this may be as easy as renaming the .asmx file. Another approach might be to implement manageability in a SOAP intermediary and when stop is received, just don't forward any more messages to the Web service.
 
Bryan Murray


From: Campana Jr., Salvatore J
Sent: Wednesday, May 04, 2005 9:38 AM
To: [email protected]; Joseph Kueser
Subject: RE: Start/Stop Operation Example?

Start/Stop has been removed from the WSDM 1.0 specs...This is why there is no example of it in the top of tree and the interop...0.5 had those operations..


From: James Lorenzen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 12:33 PM
To: Joseph Kueser
Cc: [email protected]
Subject: RE: Start/Stop Operation Example?

Kinga,

Are you aware of any examples using start/stop? The only ones I am aware of are the ones that exist in the muse 0.5 probe examples.

 

Joseph sent this question on my behalf until I could get subscribe to this mailing list.

 

Thanks, James Lorenzen.

Gestalt, LLC

 

-----Original Message-----
From: Dziembowski, Kinga [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 11:17 AM
To: Joseph Kueser
Cc: [email protected]
Subject: RE: Start/Stop Operation Example?

 

Joe,

In the past we implemented start/stop operations for the managed Web Service with the following interpretation:

When the start operation was executed on the managed Web Service – this service was available for customers and SOAP requests delivered the expected responses . When the service was stopped it was not available for the customers and the SOAP request returned SOAP fault, with the statement that the service is not available. The service itself was up and running (we did not shut the Web Services server) but from the external user point of view it was stopped=not available….

Kinga

 

 

 

Kinga Dziembowski

Hewlett-Packard Company

Applied Technology Office (ATO)

856.638.6065

[EMAIL PROTECTED]

 


From: Joseph Kueser [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 04, 2005 10:30 AM
To: [email protected]
Subject: Start/Stop Operation Example?

 

We're trying to write some fully WSDM-compliant web services, for demo purposes at this point.  We're basing our demo web services largely on what the Muse guys have put out.  But, alas, the weather station demo doesn't have start and stop operations.

 

After some thought, we realized that we do not really know what start and stop really mean :-)

 

Does anyone have a good definition of what stop and start mean in terms of WSDM web services.  And even more importantly, does anyone have an example of a start and stop implementation?

 

(Our guess right now is that start and stop pretty much mean whatever the person implementing the web service want them to mean.)

 

Thanks for your help.

 

Joe Kueser

Gestalt, LLC

Reply via email to