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

Exposing resources/services vs hiding implementation details

• To: xml-dev <xml-dev@l...>
• Subject: Exposing resources/services vs hiding implementation details
• From: Michael Champion <michaelc.champion@g...>
• Date: Tue, 5 Apr 2005 11:04:01 -0400
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=MVh/nbA8mVeMVEOfJe0lKMJt32Zcg6ZRf4cymm7D8DlCeXM/7TpezxUQtk7FU926SmmM2JhqRSMYIEv/0ONLSena2KzOoMLb5KeucdvC2Kv6H05YlZMrdMj1DbCJHB0LvKLpfYfR5WzWtYM8BzuHgTFDgeD3YrnGqwIonpoyARE=
• In-reply-to: <42528FB5.7040300@p...>
• References: <200504051139.j35BdXDR050954@s...> <42528FB5.7040300@p...>
• Reply-to: Michael Champion <michaelc.champion@g...>

On Apr 5, 2005 9:16 AM, Bill de hÓra <bill.dehora@p...> wrote:

> 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.

Why " give things of interest (the equivalent of your objects in your
domain model or your table rows in your physical data model) visible
identity?"    That seems to violate the principle of information
hiding that has been around since before OO.  It seems to be simply a
Bad Idea to expose internal details in a world where slimeballs have
proliferated  who would love to subvert your website for fun and/or
profit.  Why not hide them behind a "controller URI" that accepts
requests and gives them a going over with the polygraph and
protocoscope, then routes them to whereever the system thinks they
should be routed at this moment?

• Follow-Ups:
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Uche Ogbuji <Uche.Ogbuji@f...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Bill de hÓra <bill.dehora@p...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Jan Algermissen <jalgermissen@t...>
  • Re: Exposing resources/services vs hiding implementationdetails
    • From: Robert Koberg <rob@k...>

• 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: What Does SOAP/WS Do that A REST System Can't?
• Next by Date: xsd:redefine issue using xsd:include
• Previous by thread: Re: What Does SOAP/WS Do that A REST System Can't?
• Next by thread: Re: Exposing resources/services vs hiding implementationdetails
• Index(es):
  • Date
  • Thread