Re: WS Description and "safety"

Jonathan Marsh wrote:
> 2) The HTTP binding would take a dependency upon the safe attribute, and
> when the safe property is set to true, the HTTP method would default to
> GET, though this can be overridden when other considerations (e.g. data
> not easily serialized in a URI) apply.  This satisfied those who felt
> safety was important enough to not only remain in the family of
> Recommendations, but to have a real effect on the HTTP binding.

Can this go the other way, viz. an unsafe operation forced to use GET?

--
Regards,
Jon Hanna

"I started to accept the mess I'm in. I know that mess spelled backwards 
is ssem and I felt much better armed with that information."
- Tori Amos