W3C home > Mailing lists > Public > public-web-http-desc@w3.org > June 2006

Re: Use Cases

From: Tim Bray <tbray@textuality.com>
Date: Wed, 07 Jun 2006 11:54:29 -0700
To: Jan Algermissen <jalgermissen@topicmapping.com>
Cc: Mark Baker <distobj@acm.org>, Paul Denning <pauld@mitre.org>, public-web-http-desc@w3.org
Message-id: <D43EBEE7-DC96-4799-BDD6-78B84262DDA2@textuality.com>

On Jun 7, 2006, at 10:59 AM, Jan Algermissen wrote:

> except for HTTP and any shared MIME types, everything in a RESTful  
> system is discovered at runetime.

Who said?  I disagree entirely.  Just because the SOAP-heads blew  
WSDL doesn't mean that there's anything intrinsically wrong with the  
notion of declaring a REST interface.  It would help with things like  
tooling and testing and automation, too.

> IMHO, HTTP and the shared understanding of a MIME type *and* the  
> intention of the client developer at design time are sufficient to  
> actually implement the client side - if the design time  
> expectations do not hold at runtime this will be detected at  
> runtime. (I do not consider this a problem since there cannot be a  
> design time constraint on the runtime in a distributed system  
> anyhow so you allways need to check and expect insifficient data)

My experience differs.  When building a heterogeneous distributed  
system, I'd like to have a contract that operates at a higher level  
than a MIME type, so that when things break, you can finger-point  
constructively.  -Tim
Received on Wednesday, 7 June 2006 19:33:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:11 GMT