Lists Home |
Date Index |
Francis Norton wrote:
> Bullard, Claude L (Len) wrote:
> >Doesn't REST also use XML?
> Only for results, as far as I can make out. Unless anyone has come up
> with a standard way of sending XML parameter blocks with HTTP GETs?
You won't make much progress if you think of it as message "requests"
and "responses". Think of it as resources with representations and
addresses. Can the representations be XML? Yes. Can you send AND receive
representations? Yes. Can addresses be XML? No, not easily. But if you
think of them as addresses, then it becomes less interesting to pack
information into them as if they were messages. Pop up a level and
figure out what you are trying to do, what you want to be addressable
and what you want to be the representation.
> For those of us who get excited about sending and receiving schema-valid
> XML messages this is a bit frustrating.
The good news is that manipulating representations of resources is *even
more exciting* than sending schema-valid XML messages.
> having schema-valid GET parameters could make the web even more open -
> if my train timetable query uses a schema which enumerates all valid
> stations for the toStation and fromStation attributes, then a smart
> browser, maybe using an XForms plugin, would help me build my query, but
> I would still be able to embed or link to the resulting GET.
XForms *does* have GET support.
> Increasingly I feel that more of the value of Web Services will come
> from WSDL than from SOAP.