Didier PH Martin wrote:
>
>...
>
> Didier replies:
> So, this is not a problem, both SOAP URIs are not modified when the XSLT
> template is processed, thus, we'll obtain the same result for each
> transaction.
How do you know that? How is it communicated? Not in SOAP itself. Not in
WSDL.
HTTP communicates this merely by fiat: "GET may not have unsafe side
effects." Therefore you can call an HTTP URI 100 times or once and not
worry about its side effects. SOAP has no way to communicate this. You
must "just know". It must be communicated through prose or some other
informal means.
Let me repeat again that the point of standards is to encourage
cooperation and afix blame. If you misuse a SOAP method with serious
side effects, *you* are to blame because SOAP says nothing about it.
>...
> > > you mental model about what is a resource).
> > > a) http://meerkat.oreillynet.com/?_fl=rss
> > > b) http://meerkat.oreillynet.com/?_fl=xml
> >
> > You're talking about something unrelated. Those are two completely
> > different URLs.
>
> Didier replies:
> So, the inherent mental model that you have about resources vs. URLs is that
> a URL=resource. In that case, consider that:
As I don't think that this is really related to the issue I brought up
I'm not going to comment on it.
Paul Prescod
