W3C home > Mailing lists > Public > www-ws-arch@w3.org > February 2004

Re: Safety and WSDL

From: Bijan Parsia <bparsia@isr.umd.edu>
Date: Sun, 15 Feb 2004 08:02:47 -0500
Message-Id: <40D02C7C-5FB7-11D8-BFA2-0003936A0B26@isr.umd.edu>
Cc: <www-ws-arch@w3.org>, "'Mark Baker'" <distobj@acm.org>
To: "David Orchard" <dorchard@bea.com>

On Feb 14, 2004, at 11:11 PM, David Orchard wrote:

> Safety hits the 80/20 mark for a few things:
> - Can a client use a "safe" method as a poor man's ping?  "getStatus" 
> is a
> great example of this.

Isn't a great example of why you *wouldn't* mark your getStatus safe? 
Just because it's safe doesn't mean I want it to get hammered by a bot, 
for example. Shall we include the robots inclusion protocol? (actually 
that would be a *terrific* extension)

Some other examples given at the F2F were selecting alternative (e.g., 
GET) bindings and (client) caching. Safety probably isn't sufficient 
for either (as you certainly need expiry information as well in the 

It would be interesting to have a WSDL checker flag operations *not* 
marked as safe which had GET bindings.

Bijan Parsia.
Received on Sunday, 15 February 2004 08:02:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:58 UTC