On 12/12/06, Steve Jones <[EMAIL PROTECTED]> wrote:
> Very easy? If I've got the WSDL then I can have a test client
> _running_ in a minute or less.
What's your definition of "running"? Just because you *fetch* the API
doesn't mean you can use it with understanding straight away; there's
no limitation on the API level to what you can do, nor is there
semantics that are standardized, so how does the WSDL explain to you
their business rules? What I'm saying here is that there is no
automatic connection between the client and server; there's always a
developer, with or without sexy tools, that connects up core business
pipelines.
> The "three layers deep" bit is what is confusing me, as is the
> "someone's" which sort of implys that its owned by an independent
> third party. Could you clarify?
Just another rhetorical, really; an encrypted message on a service
that sits within a service that sits within the service, which is
especially true in secure stacks that don't want the endpoint to be
published anywhere. Most often you use the API to get to the next
service in the chain, although of course not all stacks are defined
this way. In the REST world the URL is the endpoint published on
demand (which means never officially published anywhere), and the
backend focuses around that instead of the stack. Just my clumsy way
of talking about where the focus sits in the two different
technologies. But as far as I can tell, you don't like the non-static
nature of REST.
Alex
--
"Ultimately, all things are known because you want to believe you know."
- Frank Herbert
__ http://shelter.nu/ __________________________________________________
