Re: What's the most important thing lacking in your Tcl toolbox?

tom.rmadilo@xxxxxxxxx wrote:
Apparently you can use POST/PUT/DELETE.

It's not just that you can, but that you *must*. Otherwise, it isn't REST. (Rather, you MUST if you want the associated semantics.)

I'm not sure how that works.

I'm not sure what you're confused about. You use them as the verb, instead of GET.

Does this mean the server response should contain URLs,

The original description of REST said that the result should contain URLs. So if, for example, you have (say) a directory listing of http://my.files.com/Darren/Videos, that should return data with a number of URLs all presumedly like http://my.files.com/Darren/Videos/Whatever.mpeg

or a HTTP/POST is used by the client,

If they want POST semantics, yes.

or can the client send a GET with payload?

I don't think the spec allows for a payload with GET, but I might be wrong.

Hmm, I'm guessing it doesn't matter how you deliver data, XML has
severe limitations and you have to jump through a bunch of hoops to
handle binary data or binary resources.

Right. So you deliver a textual document with URLs that point to resources that are in turn delivered with binary content-transfer-encodings.

Having just spent the last few
years working with WSDL and XML-Schema, being able to describe the
service is more important. The problem is that the more you do in
SOAP, the more difficult things get for everyone. If you could get the
description of WSDL, with a more RESTful interface, that would be
nice.

Yep. Automating that stuff would be nice. Of course, that's what XML is *supposed* to allow, but instead it's more like XML is a technology to avoid describing your transfer interfaces.

SOAP without WSDL is bound to suck.

Yes. I'm amazed at the number of one-cheek SOAP servers that interact only with themselves. Why use SOAP if it only interfaces to programs using the same library for both client and server?

And the bit of having to still rely on HTTP cookies for any sort of inter-call context (e.g., "I did a search, and now I want the next page of results") is just silly. Especially since SOAP is supposed to be transport-independent.

--
Darren New / San Diego, CA, USA (PST)
Remember the good old days, when we
used to complain about cryptography
being export-restricted?
.

Relevant Pages

  • Re: SOAP project
    ... how do i generate the XML files based on these docs? ... > webservice's WSDL document since the WSDL is the contract of the ... your job is much easier - you can create a SOAP ... > | the server as standard SOAP messages. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: SOAP to webservice
    ... Unfortunately they do not have the WSDL ... required for the SOAP header etc. Do you know of any "SOAP wrapper" ... XML document I've manually put together for testing, but I want to be able ... > class and open a socket to send the SOAP envelope to the Java server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: SOAP to webservice
    ... If the Java app builder has a WSDL file for their service, ... SOAP and simply send the values you need. ... > I am writing an application which needs to send some XML in a SOAP ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: [PHP] nuSoap client SOAP Call problem
    ... Then serialize the envelope so it looks like a SOAP request. ... The action variable is that the URL of the WSDL? ... unfortunately for some weird reason that creates the duplication. ... XML invalid any reason why its making that? ...
    (php.general)
  • RE: SP1 Problem SOAPException doesnt return quote and Umlaute correcty
    ... At the core of it is: Should SOAP fault description strings be intended ... unicode string is being URLEncoded as part of converting it to XML. ...
    (microsoft.public.dotnet.framework.webservices)