Re: Issue 169: Propose http method in the operation interface to simplify http binding.

(You guys all waited till I went to sleep to reply .. hence the barriage of
replies at once :-().

<> writes:
> same as SOAP "getStockQuote" with an endpoint of
> <>  - i.e. it
> make much sense.

Not at all! If SOAP/SMTP binding is in use it makes perfect sense to
say "send a SOAP message to that email address." However, there's no
GETting or POSTing going on there.

> Not all interfaces can be bound to any arbitary transport/serialisation
> combination.

We've tried hard to keep it protocol independent as possible. Are you
also saying that HTTP is so special that we need to break the rule for

> I still beleive it /could/ be useful to say safe=false for those of us
daft enough
> to allow buying a book using "GET".

I am prolly missing something basic .. but why is that daft? There are many
HTTP queries (using GET) which are indeed unsafe. That's why we are
careful to not say that GET ==> @safe=true. (Nor vice-versa as you pointed
out correctly .. @safe=true doesn't necessarily mean method=GET.)

In any case, @safe is asserted at the interface operation level and hence
one does not know the HTTP method (or in fact whether the binding will
be HTTP) at that time.


Received on Tuesday, 13 July 2004 00:44:05 UTC