[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What Does SOAP/WS Do that A REST System Can't?

• To: Bill de hÓra <bill.dehora@p...>
• Subject: Re: What Does SOAP/WS Do that A REST System Can't?
• From: Rich Salz <rsalz@d...>
• Date: Tue, 05 Apr 2005 10:15:19 -0400
• Cc: xml-dev@l...
• In-reply-to: <42528FB5.7040300@p...>
• References: <200504051139.j35BdXDR050954@s...> <42528FB5.7040300@p...>
• User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421

> If you decide to go the POST route, what you want to avoid  are exposing 
> controller URIs (all client requests go to one URI). At least give the 
> things of interest (the equivalent of your objects in your domain model 
> or your table rows in your physical data model) visible identity.

As a long-time fan of federated naming (XFN), I'm sympathetic to this 
approach.  In some deployments, however, we've seen that it's not 
appropriate:
	- If you're already POSTing the query, why require clients to
	  know "n" URL's rather than one?  Why "split up" the mesage?
	- There are concerns about directly exposing things like table
	  rows; I barely know SQL syntax, but I thought stored
	  procedures and views were the way to go
	- Concerns about exposing more than a single "generic" URI
	  to outside parties; more choke-points to manage, more things
	  to forward/change when deployments or architectures change
	  internally

We often talk about exposing a single generic URI and using 
content-based routing to achieve "service-oriented NAT," and find that 
customers like this approach.

	/r$

-- 
Rich Salz, Chief Security Architect
DataPower Technology                           http://www.datapower.com
XS40 XML Security Gateway   http://www.datapower.com/products/xs40.html

• Follow-Ups:
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Leigh Dodds <leigh@l...>

• References:
  • RE: What Does SOAP/WS Do that A REST System Can't?
    • From: "Marc de Graauw" <marc@m...>
  • Re: What Does SOAP/WS Do that A REST System Can't?
    • From: Bill de hÓra <bill.dehora@p...>

• Prev by Date: Re: How can I constrain publicly available schemas?
• Next by Date: Exposing resources/services vs hiding implementation details
• Previous by thread: Re: What Does SOAP/WS Do that A REST System Can't?
• Next by thread: Re: What Does SOAP/WS Do that A REST System Can't?
• Index(es):
  • Date
  • Thread